Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.8.2-EE-GA_P01
-
Fix Version/s: None
-
Component/s: Bridge
-
Labels:None
-
Environment:Linux
Glassfish 2.2.1
Firefox / IE 8
Description
We are coming across scenarios where our web application sends page updates to the clients in rapid succession. The first update contained some auto-complete fields, which when rendered included JavascriptContext calls to Ice.Autocomplete. The second update sent would change the page, which included removing the auto-complete fields. We were finding, however, that the second page update was being processed before the Ice.AutoComplete method could be executed. This resulted in Javascript errors because the element is was attempting to maintain was no longer in the DOM.
We've found that both Ice.AutoComplete and Ice.MenuBarKeyNavigator didn't check if the element was still valid before using them
We've found that both Ice.AutoComplete and Ice.MenuBarKeyNavigator didn't check if the element was still valid before using them
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Patch applied against 1.8.2-EE-P01, which checks if the elements can be found.
These changes address this issue for us.