Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: EE-4.0.0.GA
-
Fix Version/s: 4.1
-
Component/s: ACE-Components, Sample Apps
-
Labels:None
-
Environment:Jenkins EE-4.0 Trunk Build # 194
Applications: showcase
Browsers: Firefox34, Chrome41
Server: Tomcat 7/ IBM WebSphere 8.5.5.4
-
Assignee Priority:P2
Description
Browser console warnings are visible when navigating to certain demo pages in showcase.
1) ace:textEntry > Secret; ace:tooltip > Global; ace:dialog > Overview:
Chrome:
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check http://xhr.spec.whatwg.org/. bridge-support.js.jsf?ln=ice.core&v=4_0_0_150311:1061
2) ace:dialog > Modal & Movable:
Firefox34/Chrome41:
JQMIGRATE: jQuery.fn.andSelf() replaced by jQuery.fn.addBack()
jquery...._150311 (line 190)
3) ace:ajax > Overview; ace:menu > Effects: warnings when moving the cursor;
ace:dataTable > Column Reorder: warnings when reordering columns:
FF34/Chrome41:
JQMIGRATE: jQuery.fn.andSelf() replaced by jQuery.fn.addBack()
jquery...._150319 (line 190)
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The issue #1 is not related to any component code in particular. It happens whenever a resource is loaded dynamically (asynchronously). The message is displayed by the browser itself, not by jQuery. The root cause is passing async=false when opening an XMLHttpRequest. This is done by the code in bridge-support.js, which handles loading resources dynamically. The solution could consist in passing async=true when loading these resources, as mentioned in http://xhr.spec.whatwg.org/
Developers must not pass false for the async argument when the JavaScript global environment is a document environment. User agents are strongly encouraged to warn about such usage in developer tools...
Assigned to Mircea to review and adopt the async=true fix for the bridge-support.js file as described above.
The code triggering the synchronous AJAX requests are extractAndEvaluateScripts and extractAndAppendStyles in fixjsf.js file. These functions need to load and evaluate the received content before the rest of the updates are processed to ensure that these updates have access to the new JS or CSS definitions.
So, we cannot use asynchronous AJAX requests in this case.
Verified, ICEfaces4 trunk r45816, Chrome43.
r45572: disabled all JQMIGRATE warning messages.