Noticed this as well, and it started causing the problem I posted about yesterday: http://code.google.com/apis/maps/documentation/javascript/forum.html?place=topic%2Fgoogle-maps-js-api-v3%2FqxcrhCMEEjo%2FdiscussionAre you guys able to use the Autocomplete popup when the window's scrollY is greater than 0?
--To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/EZ0-DyXGkgIJ.
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 google-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/novijabp8J4J.
This change was expected. Release notes will be coming out soon.
-- Luke
On Thu, Jun 30, 2011 at 4:44 PM, Johannes Schill <johanne...@gmail.com> wrote:
Does this mean the pac-container is supposed to be right before the closing body-tag in the future or was that change an expected one?
Cheers
Johannes
Den torsdagen den 30:e juni 2011 kl. 00:42:38 UTC+2 skrev Luke (Google Employee):
We are looking into the scroll issue.Thanks.
-- Luke
On Thu, Jun 30, 2011 at 2:36 AM, Ross Allen <rea...@gmail.com> wrote:
Noticed this as well, and it started causing the problem I posted about yesterday: http://code.google.com/apis/maps/documentation/javascript/forum.html?place=topic%2Fgoogle-maps-js-api-v3%2FqxcrhCMEEjo%2FdiscussionAre you guys able to use the Autocomplete popup when the window's scrollY is greater than 0?--To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/EZ0-DyXGkgIJ.
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 google...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/zia1EC89M-8J.
-- Luke
-- Luke
-- Luke
To post to this group, send email to goog...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/novijabp8J4J.
To post to this group, send email to google...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.
It's basically because we use different styles applied to the pac-container, depending on which template is used. Sometimes the pac-container is relatively positioned to another container, sometimes its X pixels wide and sometimes its Y pixels wide, sometimes the top/left-values need to be overridden etc. I suppose i can rewrite my code and work around it by adding a class to the body-tag or to the pac-container itself + some scripting to position the container, but it would have been smooth with an appendTo- and/or optionalCssClass-option to avoid the hacking and keep the markup as free from sin as possible.
To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/gRuTWh5cW2wJ.