Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 2.0.1
-
Fix Version/s: 3.2
-
Component/s: ACE-Components
-
Labels:None
-
Environment:ACE fileEntry, ace-showcase, IE9
-
Assignee Priority:P3
Description
When a JSF page is first rendered, it doesn't know if the browser has cookies enabled, for storing the session id, so it renders the jsessionid into every single link in the page. Then, after the first postback, it detects that cookies are enabled, and stops rendering the jsessionid into every link, and our dom diff sees that lots of the page have changed, and sends all the changes to the browser. Usually that doesn't cause any problems.
http://localhost:8080/ace-showcase/fileEntry.jsf
But, in IE9, if the very first page you bring up has an ACE fileEntry in it, and the very first postback is from uploading a file, then the custom fileEntry ajax technique does not succeed in applying the dom updates to the page. And upload after that, will update the page. There is no problem in Firefox, WebKit, or older versions of IE.
http://localhost:8080/ace-showcase/fileEntry.jsf
But, in IE9, if the very first page you bring up has an ACE fileEntry in it, and the very first postback is from uploading a file, then the custom fileEntry ajax technique does not succeed in applying the dom updates to the page. And upload after that, will update the page. There is no problem in Firefox, WebKit, or older versions of IE.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion