| Issue 1020: | Bug: GInfoWindow.maximizeend event fired before maxcontent is attached to DOM | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
Issue: When user maximizes an infoWindow, after the 'maximizeend' event is fired, it is expected that the content of the max content should be available in DOM and can be accessed by document.getElementById. It is OK that it will not be available at 'maximizeclick' event, but SHOULD be available at 'maximizeend' event. In another words, the 'maximizeend' event should be fired AFTER the content is attached to DOM, not the other way. See the following example: http://ags.gmaps.googlepages.com/issue_maximizeend.html It's causing some problems if some sort of AJAX operations is needed to modify parts of the content that is constructed by html. What version of the API are you using? (most recent as of 01/22/2009, v 2.142c) What operating system and browser are you using? XP firefox/IE. |
||||||||||||||
,
Jan 27, 2009
Replicated and reported, thanks.
Status: Accepted
Labels: Internal-1606385 |
|||||||||||||||
,
Feb 11, 2009
(No comment was entered for this change.)
Status: FixedNotReleased
|
|||||||||||||||
,
Feb 24, 2009
Nianwei- This bug affected something in ArcGISLink, right? Can we change that demo to use 2.147?
Status: Fixed
Labels: Fixed-2.147 |
|||||||||||||||
,
Feb 25, 2009
V2.147 fixed the problem. The bug: http://ags.gmaps.googlepages.com/issue_maximizeend.html?v=2.142c The fixed: http://ags.gmaps.googlepages.com/issue_maximizeend.html?v=2.147 The 2.x: http://ags.gmaps.googlepages.com/issue_maximizeend.html?v=2.x That sample can be used as a recommended way to report bug to check API versions. |
|||||||||||||||
 Sign in to add a comment
|
|||||||||||||||
