Yes, I remarked on this the other day, and I was pointed to 3rd party
methods, one of which had "tab" buttons inside the bubble. Although
this approach will work, it no longer "looks" like the standard Google
Tabbed InfoWindows. This means that v3 apps will look different than
v2, and that different developers may use different methods, and a
general loss of a consistent "look and feel".

I think Google should provide "Tabbed InfoWindows" in a way that
recreates the v2 experience, or they should provide an explanation why
they are not doing so. Is there a problem with the new API code
architecture that makes it difficult for Google to provide these
tabbed bubbles?

I added this request the other day (# 2103). I hope other folks will
vote for this issue at:

http://code.google.com/p/gmaps-api-issues/issues/detail?id=2103&q=apitype%3AJavascript3&colspec=ID%20Type%20Status%20Introduced%20Fixed%20Summary%20Internal%20Stars

David Coggeshall
SFC MapLab Project
-- 
You received this message because you are subscribed to the Google Groups 
"Google Maps JavaScript API v3" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-maps-js-api-v3?hl=en.


Reply via email to