Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.3
-
Fix Version/s: EE-3.3.0.GA, 4.0.BETA, 4.0
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Any
-
Assignee Priority:P2
Description
There is a JS error in all IE browsers when navigating the ace:gMap demos and re-sizing the browser window:
Error in IE9:
Message: DOM Exception: NOT_FOUND_ERR (8)
Line: 1
Char: 1
Code: 0
URI: http://10.18.39.149:8080/showcase/showcase.jsf?grp=aceMenu&exp=mapBean
Error in IE10:
Message: NotFoundError
Line: 17
Char: 473
Code: 0
URI: http://10.18.39.149:8080/showcase/showcase.jsf?grp=aceMenu&exp=mapBean
It happens after navigating to a different demo and then resizing the window or maximizing/restoring it. It doesn't happen in the overview demo at first, but it does happen after navigating to another demo and then returning to the overview demo and resizing the window.
Error in IE9:
Message: DOM Exception: NOT_FOUND_ERR (8)
Line: 1
Char: 1
Code: 0
URI: http://10.18.39.149:8080/showcase/showcase.jsf?grp=aceMenu&exp=mapBean
Error in IE10:
Message: NotFoundError
Line: 17
Char: 473
Code: 0
URI: http://10.18.39.149:8080/showcase/showcase.jsf?grp=aceMenu&exp=mapBean
It happens after navigating to a different demo and then resizing the window or maximizing/restoring it. It doesn't happen in the overview demo at first, but it does happen after navigating to another demo and then returning to the overview demo and resizing the window.
When turning debugging on, the IE developer tools window shows that the error actually happens in a dynamically loaded google source file, apparently via an 'eval'.
The error happens is not related to any ace:gMap subcomponent in particular. If the other demos are modified to just contain a simple ace:gMap instance with no other components, the error still happens.
According to various pages, the error 'DOM Exception: NOT_FOUND_ERR (8)' is thrown because a node cannot be found. I suppose that the google gmap code registers some on-resize events on the window or document objects, which when triggered update the map instance that registered the event and the map is resized or re-centered. So, when the original node cannot be found, this error is thrown by IE.
We've seen similar issues before, which have to do with the showcase navigation style. Perhaps, this issue could be solved by registering an onelementRemove event in our framework to remove all listeners related to a gmap instance, especially those registered on the window or document objects.