Fixed
Status Update
Comments
mb...@gmail.com <mb...@gmail.com> #2
Can you track these events by assigning event listeners on the map container? For
example:
google.maps.event.addDomListener('map_canvas', 'mousemove', function(e) {
// code here
});
Granted, it'll take a bit more code on your end to determine whether the mouse is
within map container boundaries, but this seems like a feature you can add yourself.
example:
google.maps.event.addDomListener('map_canvas', 'mousemove', function(e) {
// code here
});
Granted, it'll take a bit more code on your end to determine whether the mouse is
within map container boundaries, but this seems like a feature you can add yourself.
en...@google.com <en...@google.com> #3
I have tried but my event handlers conflict with yours. The pixel arithmetic is
messy. It requires an additional OverlayView for the "fromPixelToLatLon" conversion.
You already have the same information for "click" & "dblclick" event handlers.
The browsers measure pixel offsets differently. Internet Explorer measures pixel
offsets relative to the parent DIV. Firefox measures pixel offsets relative to the
DIV containing the corresponding tile. An extra DIV is required in order to simplify
the Firefox arithmetic. Unfortunately, it covers your click layer which causes it to
fail.
messy. It requires an additional OverlayView for the "fromPixelToLatLon" conversion.
You already have the same information for "click" & "dblclick" event handlers.
The browsers measure pixel offsets differently. Internet Explorer measures pixel
offsets relative to the parent DIV. Firefox measures pixel offsets relative to the
DIV containing the corresponding tile. An extra DIV is required in order to simplify
the Firefox arithmetic. Unfortunately, it covers your click layer which causes it to
fail.
ed...@google.com <ed...@google.com>
pr...@gmail.com <pr...@gmail.com> #4
OK, we'll consider it.
Thanks!
Thanks!
zw...@google.com <zw...@google.com> #5
The pixel arithmetic is not trivial. Browser differences must be accommodated.
Look at:
http://www.polyarc.us/polycluster/event.html
It is a lot of work just to track mouse coordinates. It is incompatable with your
event listeners.
Look at:
It is a lot of work just to track mouse coordinates. It is incompatable with your
event listeners.
Description
Chrome 43.0 / Firefox 38.0 / Safari 8.0
Retina MacBook ( OS X 10.10 )
Rectangles and Circles with option { strokePosition: google.maps.StrokePosition.OUTSIDE } are rendered incorrectly
please check:
and attached Screenshot
OK:
API 3.19 / 3.20 - Chrome / Firefox / Safari - Retina Macbook ( OS X 10.10 )
API 3.21 - Chrome / Safari - iPad 2 ( iOS8.3 ) !