Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: EE-1.8.2.GA_P04
-
Fix Version/s: EE-1.8.2.GA_P05
-
Component/s: ICE-Components
-
Labels:None
-
Environment:Chome 18
-
Assignee Priority:P1
Description
A JavaScript error is thrown when calling the iceSubmitPartial() JaavScript API on load of a panelPopup. The error is thrown only in Chrom 18, all other browsers and older Chome versions do not show the error. The error prevents a valueChangeListener from being called.
-
Hide
- Case11198Example.war
- 6.66 MB
- Arran Mccullough
-
- META-INF/MANIFEST.MF 0.1 kB
- META-INF/context.xml 0.1 kB
- UiUtils.js 0.6 kB
- WEB-INF/classes/.../example/TestBean.class 2 kB
- WEB-INF/faces-config.xml 0.7 kB
- WEB-INF/lib/FastInfoset.jar 285 kB
- WEB-INF/lib/backport-util-concurrent.jar 319 kB
- WEB-INF/lib/commons-beanutils.jar 226 kB
- WEB-INF/lib/commons-collections.jar 558 kB
- WEB-INF/lib/commons-digester.jar 140 kB
- WEB-INF/lib/commons-discovery.jar 75 kB
- WEB-INF/lib/commons-fileupload.jar 56 kB
- WEB-INF/lib/commons-lang.jar 240 kB
- WEB-INF/lib/commons-logging.jar 52 kB
- WEB-INF/lib/icefaces-comps.jar 1.76 MB
- WEB-INF/lib/icefaces-facelets.jar 596 kB
- WEB-INF/lib/icefaces.jar 1.23 MB
- WEB-INF/lib/jsf-api-1.2.jar 355 kB
- WEB-INF/lib/jsf-impl-1.2.jar 837 kB
- WEB-INF/web.xml 4 kB
- welcomeICEfaces.xhtml 3 kB
-
- Case11198Example.zip
- 20 kB
- Arran Mccullough
-
- IceSubmitPartialError.jpg
- 110 kB
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The fix tests for the existence of target element (in Element.adaptToElement()) before trying to verify if the event is DOM related.
Show
Mircea Toma
added a comment - - edited The fix tests for the existence of target element (in Element.adaptToElement()) before trying to verify if the event is DOM related.
The solution may solved the problem with Chrome, but caused a problem with rowSelector event on Firefox (tested on ver.15 and 16): Nothing happens, when clicking a table row, no request is generated..
The issue is caused by the global window.event variable that has its value set to a XMLHttpRequestProgressEvent during the second submit. When this non-DOM event is wrapped the code looking up the node's name invoked later on, fails.
The applied fix tests if the event to be decorated is truly a DOM event, if not, a generic unknown event decorator is used.