Styling body{margin: 0 auto; max-width: 800px;} yields a left offset > 0 for
the pac-container when the window.width > 800 and the target input.left =
0. I see this problem in both Chrome and FF (haven't tested IE).
It seems the pac-container's position is being calculated using the window
offset of the target -- which works fine until window and body don't share
the same origin.
Despite the conclusions reached in Places Autocomplete JS - The
pac-container changed dom-position
recently<http://groups.google.com/group/google-maps-js-api-v3/browse_thread/thread/89b2249d390f4e1a/6ecb3439fd6de903>),
I think all would work better if the API simply inserted the pac-container
after the target *with no styles set*. Inserting after the target means the
container always ends up in a predictable place, one easily found in the DOM
no matter when the binding executes in the flow. Most importantly, leaving
all styling to the page would avoid these kind of issues entirely.
Regards,
George
--
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/-/XCzUQyF33hEJ.
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.
