ICEfaces
  1. ICEfaces
  2. ICE-11404

ace:fileEntry issues on Edge version 42+

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major 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

      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

        Activity

        Arturo Zambrano created issue -
        Arturo Zambrano made changes -
        Field Original Value New Value
        Assignee Arturo Zambrano [ artzambrano ]
        Arturo Zambrano made changes -
        Fix Version/s 4.3 [ 13096 ]
        Fix Version/s EE-3.3.0.GA_P06 [ 13114 ]
        Arturo Zambrano made changes -
        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. This 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
        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
        Judy Guglielmin made changes -
        Support Case References Support Case 14341:- https://icesoft.my.salesforce.com/5000g00001tqtyK
        Repository Revision Date User Message
        ICEsoft Public SVN Repository #52478 Thu Jun 14 14:22:11 MDT 2018 art.zambrano ICE-11404 adjusted conditional to allow the processing of the response, initiated by fileEntry, on Edge browsers (while still working on other browsers as well)
        Files Changed
        Commit graph MODIFY /icefaces4/trunk/icefaces/ace/component/resources/icefaces.ace/fileentry/fileEntry.js
        Hide
        Arturo Zambrano added a comment -

        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.

        Show
        Arturo Zambrano added a comment - 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.
        Arturo Zambrano made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ken Fyten made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            Arturo Zambrano
            Reporter:
            Arturo Zambrano
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: