Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.0
-
Fix Version/s: EE-4.0.0.GA, EE-3.3.0.GA_P03, 4.1
-
Component/s: ICECORE-Components
-
Labels:None
-
Environment:Tomcat 7, ICEfaces 4 trunk r43291. IE 10/11
-
Assignee Priority:P2
-
ICEsoft Forum Reference:
Description
icecore:push demo is not running properly in IE 11. The demo appears to submit twice when doing any updates, no matter which push strategy is chosen. When choosing update "Page every second" the page updates twice per second. This is not an issue in other browsers UNLESS they are launched after the page is used in IE 11. Meaning that when icecore:push is deployed on a clean server only using FF, Chrome or IE 10 the issue is not seen. However, launch IE 11, observe the issue, then launch other browsers and the issue will be seen as well.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
This issue can be caused by starting the demo in a browser, then closing the browser, then opening a new browser and running the demo again. The second browser will double update the charts.
Modified icecore:push demo to generate a notification group per window. This avoids having the notifications generated by one window to be broadcasted to the rest of windows or browsers connected to the demo.
Tested with ICEfaces 4 tag r43311
Reopening for these issues:
1.) The page updates too often when only used in IE 11.
This can be reproduced by installing showcase on Tomcat 7 and launching IE 11.
Navigate directly to icecore:push and choose "update page every second". After the first update the page starts to update 2 times per second.
2.)The issue is still present where one page will update another page in the group.
This can be reproduced by installing showcase on Tomcat 7 and launching FF.
Navigate directly to icecore:push and choose "update page every second". The demo runs as expected.
Next open another tab in FF and navigate directly to icecore:push.
The demo in the first tab will stop updating when the demo in the 2nd tab starts.
The demo in the second tab updates approx. twice per second.
Modified pushID expiry mechanism to reset pushID responsiveness counter once a confirmation is received (instead of just decrementing the corresponding un-responsiveness counter). Increased un-responsiveness threshold to 10 since the browsers are dropping 'storage' events during high local storage activity. Modified 'storage' event callbacks to filter on name to avoid redundant callback invocations. Also modified PushWindowScopeBean to shutdown timer on window disposal.
ICEfaces-4.0.0 tag Jenkins Build#4 (r.43337) testing results:
The initial issue from description still exists: in IE11, when opening the icecore:push demo in first browser window, and selecting "Update page every second", the push updates appear to be more frequent than once/second. When opening this demo in a second separate IE11 window and selecting "Update page every second", the frequent updates are visible on the second window, while on the first window the push updates stop. The push updates remain stopped on the first window also when closing the second window.
Testing using the same step in other browsers (Chrome38, FF33, IE10):
- the more frequent push updates cannot be reproduced in any of these browsers.
- in all these browsers, after the demo is loaded in 2 separate windows and push updates are selected for "every second", the push updates work fine in both opened windows for about 10-15 seconds, afterwards they stop updating on both windows.
Tested with ICEfaces 4 trunk r43375. IE 11 issue still exists
To reproduce issue:
Launch showcase in IE 11.
Navigate to icecore:push > Overview demo.
For Select push strategy choose "Update page every second".
Observe that the update appears to happen twice per second instead of once per second.
Open a new IE 11 browser.
Observe that the initial demo now updates once per second, then eventually stops.
Also note a forum report with a similar issue (added to the Forum link field).
Created new JIRA case for the push issue: PUSH-343 .
It seems that IE11 is not detected properly by the inter-window communication mechanism. Because of this the 'storage' event callback for the window that triggers the events is invoked twice, by the framework and the browser.
Detect IE11 also to make sure the 'storage' event callback is not invoked in the window triggering the events.
Verified ICEfaces 4 trunk r43633. Tomcat 7, IE 11, 10, FF 33, Chrome 39.
Issue still exists when using IE9:
http://www.icesoft.org/JForum/posts/list/22731.page#79652
I cannot reproduce the issue.