Details
Bug
Major
Description
When an ICEfaces application is initially displayed or the Content Cache is cleared, the following exception may be thrown during iceSubmit()
couldn't find container for property: bridge
Mircea, what initialization steps need to take place for the "bridge" property to exist?
This may be a browser bug, but it may also be desirable to find a workaround (such as an attempt to reinitialize the bridge).
It does not appear to occur on the simulator.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Mircea Toma [ mircea.toma ] |
workaround appears in scope for DR2.
| Fix Version/s | 1.8DR#2 [ 10142 ] |
The problem occurs on this line of synchronizer.js
if (this.historyFrame.location.hash.length > 0) this.reload();
catching an exception here and proceeding would seem to be acceptable given that bridge initialization is more vital than history maintenance.
Mircea, can you comment on the side effects of having the reload() not running to completion?
Ice.Document.Synchronizer detects if the back button was used, if so it will reload the entire page to make sure the page is in sync with the version on the server.
The side effects of failing to synchronize the page could be that some updates cannot be applied to the browser's DOM. Although if you can't access the historyFrame that it could mean, heuristically, that the page was freshly re/loaded.
| Repository | Revision | Date | User | Message |
| ICEsoft Public SVN Repository | #17869 | Thu Nov 06 08:17:03 MST 2008 | ted.goddard | ignoring backbutton failure on BlackBerry ( |
| Files Changed | ||||
MODIFY
/icefaces/trunk/icefaces/bridge/src/synchronizer.js
|
Checked in a change where the history frame reload failure is simply logged. If testing shows that the back button does not work as expected on the BlackBerry, we can create specific JIRAs.
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Fix Version/s | 1.8 [ 10161 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Assignee | Mircea Toma [ mircea.toma ] |
In application.js the following change:
try
{ var documentSynchronizer = new Ice.Document.Synchronizer(window.logger, sessionID, viewID); }catch (e)
{ alert("synchronizer " + e); }occasionally displays
"synchronizer Same-origin policy violation", so perhaps the history iframe is in a strange state due to not being cached.
Mircea, what problems would arise if the documentSynchronizer was not initialized? A sufficient workaround may be to catch the above exception and log it; at least the bridge would otherwise initialize.