Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.6
-
Fix Version/s: 1.6.1
-
Component/s: Bridge
-
Labels:None
-
Environment:Opera, Mobile Opera
-
ICEsoft Forum Reference:
-
Affects:Documentation (User Guide, Ref. Guide, etc.), Compatibility/Configuration
-
Workaround Exists:Yes
-
Workaround Description:Run applications in concurrentDOMViews=false mode.
Description
From the forum post:
I just noticed that the server push doesn't always work with Opera (and mobile) anymore, it's working fine on other browser. I tried the auction monitor and timezone tutorial and they work with Opera, the problem comes when changing view.
So I used the timezone7 tutorial and added 2 pages that go from one to another with just showing the clock. It's working fine with IE and Firefox, but on Opera the clocks stops ticking when going to the second page.
Here's a sample WAR to witness the problem
BTW it was working fine with v1.5.3
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Well, I actually fixed this issue in commit #14622 (icefaces/bridge/src/application.js) by relying on document.unload to shutdown the Bridge (formerly document.onbeforeunload was used).
There's one remaining limitation, on document.onbeforeunload the Bridge will send the list of views that need to be disposed (when running in concurrentDOMViews=true) but Opera won't send the message because it doesn't support document.onbeforeunload feature at all. If the user will reload the page repeteadly it will cause rapid memory increase on the server side.
See described limitation.
Re-opening case since it is a blocker for the AjaxWorld demo on mobile opera.
concurrentDOMViews=false does not appear to be a workaround.
http://component-showcase.icefaces.org
does not use concurrentDOMViews, yet the progress bar ceases to work when the page is reloaded.
confirmed that Ajax Push does not work after page reload in Mac Opera 9.23.
Remove the blocking connection marker on bridge load so that everytime a new window (== bridge instance) is opened the blocking connection will be re-established.
Opera doesn't invoke document.unload listeners when is changing the page or closing the window. The Bridge relies on this behaviour to clear up the marker cookie used to inform the other windows if the persistent connection is started or stopped.