| Issue 3120: | Cursor does not change for markers on a non-draggable map | |
| 4 people starred this issue and may be notified of changes. | Back to list |
When a non-draggable map is created by setting its "draggable: false" option, markers added to that map do not change their cursor on mouse hover. In the past, the default behavior was to use the cursor: "pointer". Even explicitly setting that cursor for the marker does not work. This became a problem as of version 3.4 example: http://jsfiddle.net/c7Rqm/
Mar 25, 2011
The same case is happening for me because Google will think like if the draggable property is false then whats the necessity to change the cursor. So that's the reason Google is making the cursor to default. But at least they can default to pointer.
Jun 8, 2011
Confirming that I'm seeing this same behavior. Seems like a pretty serious oversight considering that most POIs in GMaps aren't draggable and have the pointer cursor... I'm not sure what the thought process is behind non-draggable pointers not having cursors (especially if they click handlers assigned, but even then cursor changing seems orthogonal to draggability).
Jun 8, 2011
Ahh, after a quick poke through the element inspector figured out what's going on. Because of the way markers are "optimized" now, cursors don't work. I'm assuming that when draggable is set to true, optimized is automatically set to false. When cursor is set, this should probably also be set so that they work (and maybe noted in the docs). In the meantime, if you add an "optimized: false" flag, markers will render individually and the assigned cursor will display as it should.
Jul 4, 2011
(No comment was entered for this change.)
Status:
Fixed
Labels: Fixed-3.5 |
|
| ► Sign in to add a comment |
Labels: Internal-4064161