Rich inplace input problem with IE

[floryn]

I am using RichFaces 3.2.2.GA with JBoss Seam 2.0.2.SP2 on Weblogic 9.2. When creating a page with <rich:inplaceSelect> or <rich:inplaceInput>, everything seems to work great in FireFox and Opera.

But in IE 6, there seems to be a problem with its ability to load images from the CSS styles of these inputs. IEXPLORE.EXE consumes 280MB for this page, and is incredibly slow. When moving the mouse over the inplace inputs or selects, IE begins to try to load 10-15 images, and this is multiplied when I mouse-over several of these components. The memory consumed by IE continues to increase when these images are loaded, to well above 500MB.

Below are three different items displayed by IE that it is trying to load:
/a4j/g/3_2_2.GAorg/richfaces/renderkit/html/images/b
/a4j/g/3_2_2.GAorg/richfaces/renderkit/html/images/bg
/a4j/g/3_2_2.GAorg/richfaces/renderkit/html/images/bg_

Any ideas on how to get around this? I thought I had somehow solved the problem after rebooting my computer, but others trying to load the page with IE continue to have this problem.

I do not have this problem with the richfaces demo site.

[nbelaevski]

Hello,

Can you please try with another application server, e.g. JBoss or Glassfish?

[floryn]

I am having trouble making my application play with Glassfish, but I did try using an older version of richfaces. I switched to 3.2.0.GA and the excessive image loading in IE does not seem to be a problem anymore. However, the page becomes very slow in IE (unusably slow), and the memory used continues to increase as I test the inplace elements.

Just an FYI, my page consists of a <rich:tabPanel> containing a <rich:dataList>. Each line in the dataList contains one <rich:inplaceSelect> and one <rich:inplaceInput>. Even for a short list of 4-5 entries, IE can become unresponsive between clicks.

It seems that there are quite a few bugs in this version for the inplace selects and inputs for both IE and FireFox that do not appear in the latest version, 3.2.2.GA.

[nbelaevski]

Hello,

I've created an issue to check the problem: https://jira.jboss.org/jira/browse/RF-4858

Please watch it to track progress