Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.2, EE-3.3.0.GA_P05
-
Fix Version/s: 4.3, EE-3.3.0.GA_P06
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Any
-
Support Case References:Support Case 14341:- https://icesoft.my.salesforce.com/5000g00001tqtyK
Description
With a recent update of the Edge browser to version 42+ and its EdgeHTML engine to version 17+ the ace:fileEntry component becomes unresponsive after submitting a file in the 3.3 codebase, while in the 4.2 codebase, it's just not possible to upload files. These issues were not present on Edge version 41+ with EdgeHTML engine version 16+.
These issues can be easily seen on the public showcase demos for both versions when using Edge 42+:
http://icefaces-ee3-showcase.icesoft.org/showcase.jsf?grp=aceMenu&exp=fileEntry
http://icefaces-showcase.icesoft.org/showcase.jsf?grp=ace:fileEntry
These issues can be easily seen on the public showcase demos for both versions when using Edge 42+:
http://icefaces-ee3-showcase.icesoft.org/showcase.jsf?grp=aceMenu&exp=fileEntry
http://icefaces-showcase.icesoft.org/showcase.jsf?grp=ace:fileEntry
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
r52477, r52578: adjusted conditional to allow the processing of the response, initiated by fileEntry, on Edge browsers (while still working on other browsers as well)
In the file entry client-side code, we were checking to see if the response was an XMLDocument, before processing it. On the latest version of Edge (42), the response was a regular Document object, even though the contents were the same XML contents of a typical ICEfaces response. This conditional was modified to circumvent this change in the Edge browser.