Fixed
Status Update
No update yet.
Comments
da...@google.com
Oh wow, it looks like it was just fixed, right after I filed this bug!
es...@gmail.com
Closing this bug. Glad it is working for you now.
da...@google.com
I'm sorry it looks like this bug still happens. Is there a way to reopen it?
es...@gmail.com
There are even tab 'scripts' without any javascript. Pure CSS implementations with
:target pseudoselector.
http://tutorials.mezane.org/tabbed-navigation-using-css/
One påossible generic recommendation might be to register a 'click' handler by
addDomListener() to the map tab. Some timeOut may be needed.
:target pseudoselector.
One påossible generic recommendation might be to register a 'click' handler by
addDomListener() to the map tab. Some timeOut may be needed.
da...@google.com
In the case of a tabbed UI without JavaScript, can you register a 'click' listener
onto the tab's HTML element and have the event handler function trigger the Map
resize event?
Do you have a link to a sample application for which this is a problem? I'm certain
we can find a reasonable solution.
onto the tab's HTML element and have the event handler function trigger the Map
resize event?
Do you have a link to a sample application for which this is a problem? I'm certain
we can find a reasonable solution.
da...@google.com
Just to clarify what was "Fixed" in the release, here are the notes again from my
comment above:
"In the upcoming release, the team decided to address this issue without the use
explicitly defining a 'size' property under MapOptions. This property has been
removed as a result. Map container dimensions are better tracked and updated.
Triggering the Map 'resize' event should work properly once again after toggling the
container's display field."
No "size" property was added or documented. The Map "resize" event should be
triggered, which should now work correctly for map containers initially hidden with
display:none.
comment above:
"In the upcoming release, the team decided to address this issue without the use
explicitly defining a 'size' property under MapOptions. This property has been
removed as a result. Map container dimensions are better tracked and updated.
Triggering the Map 'resize' event should work properly once again after toggling the
container's display field."
No "size" property was added or documented. The Map "resize" event should be
triggered, which should now work correctly for map containers initially hidden with
display:none.
es...@gmail.com
I know the case was closed but would you please consider the 'size' option once again.
thanks,
Esa
Description
Most of the the tab scripts seem to switch the selected containers between
{display: none} and {display: block}. Initializing a map in a container in
{display: none} status would need triggering 'resize' event when (after)
display is changed.
However most of the tab scripts do not provide any easy method to trigger
the 'resize'.
There is 'size' option in MapOptions and it seems to work perfect. It would
make 'resize' event triggering unnecessary in most cases. I do not
recommend that for people because that is not documented.
Please document 'size' option.