Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.1, EE-4.1.0.GA
-
Component/s: MOBI-Components, Sample Apps
-
Labels:None
-
Environment:ICEfaces 4 trunk r49141, Tomcat 8. Chrome 52 desktop and mobile browsers.
-
Assignee Priority:P2
Description
The mobile showcase has icons beside each of it's demos. When using Chrome browser, after viewing a demo then returning to the menu, the icons are no longer displayed. Refreshing the browser clears the issue. This issue can not be reproduced 100% reliably and may be related to latency.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The issue was in ResourceOrdering resource handler, the resources that have no dependency meta-data defined are colaesced in a different ordered than the order used for the page load. This in effect changes the entire content of the colesced resource thus causing a reload.
The applied fix normalises the order for the resources that have no dependency meta-data.
Show
Mircea Toma
added a comment - The issue was in ResourceOrdering resource handler, the resources that have no dependency meta-data defined are colaesced in a different ordered than the order used for the page load. This in effect changes the entire content of the colesced resource thus causing a reload.
The applied fix normalises the order for the resources that have no dependency meta-data.
Verified ICEfaces 4 trunk r49310. Tomcat 8, FF 47, MS edge, IE 11, 10, Chrome 53 desktop browser, android nexus 5 with Chrome browser.
Show
Liana Munroe
added a comment - Verified ICEfaces 4 trunk r49310. Tomcat 8, FF 47, MS edge, IE 11, 10, Chrome 53 desktop browser, android nexus 5 with Chrome browser.
When any of the mobile demos are accessed the coalesced.css resource is reloaded for some reason. Chrome is fetching this large resource through an asynchronous AJAX (during an partial update) which causes the browser to apply the CSS styles after the page was reflowed. This explains why the icons rendered with the help of CSS are not shown.
Still, when new components are rendered the resources they require are supposed to be referenced separately from the coalesced resource to avoid re-loading such a large file again. Need to investigate why this occurs.