The default bug view has changed. See this FAQ.

reordering markers while editing custom google maps broken

RESOLVED FIXED

Status

()

Core
Event Handling
RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: dbaron, Unassigned)

Tracking

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

7 years ago
I originally described this in bug 517737 comment 20:
> Another set of Google Maps steps that regressed on the same day, but don't seem
> to be fixed by the pair of patches above:
>  (1) while logged in to google, create a map using the "My Maps" - "Create a
> Map" feature in http://maps.google.com/
>  (2) create at least 2 placemarks in that map
>  (3) while editing, drag the placemarks up and down to reorder them
> 
> The dragging of placemarks while editing a map broke in the same regression
> range, but isn't fixed by attachment 420271 [details] [diff] [review] plus attachment 420273 [details] [diff] [review].
While following the above STR I came across bug 540491. So you may need to create the custom map in another build before hand to see this bug.
OS: Linux → All
Hardware: x86 → All
The problem is that google maps is calling setCapture on a display: none element. I checked in IE and calling setCapture on a display: none element does work there.

Comment 3

7 years ago
(In reply to comment #2)
> The problem is that google maps is calling setCapture on a display: none
> element. I checked in IE and calling setCapture on a display: none element does
> work there.

I don't think real mouse events can target elements without frames. Similar to bug 540491, we only capturing to work while the mouse is pressed to prevent abuse, so if setCapture is being called outside of a mousedown, it won't have any effect.
I think setCapture is being called from a mousedown, just that the element that the mousedown is on is different from the one that gets setCapture called on it.

Updated

7 years ago
Duplicate of this bug: 542923
Is this same bug?
When you are creating "My Map" on Google Maps and when you select "Add a placemark" the icon stays there even if you're moving mouse?
Here is a screenshot: http://img836.imageshack.us/f/googlemapse.jpg/
I think that is bug 540491.

Updated

6 years ago
Duplicate of this bug: 643728

Updated

6 years ago
Duplicate of this bug: 646800
Depends on: 540491

Comment 10

6 years ago
Hi, I'm making the fix in Google Maps for bug 540491. Checking all the setCapture uses fixes this bug too, I'm hoping the fix will be live within a week.

Comment 11

6 years ago
FF 4.0, XP pro sp3, fully patched.
I have been using a custom map with FF 3.x for a long time, no problem.  Now, if I try to edit and add a marker, the marker is placed under the icon.  If I scroll the map to show it, then try to grab it with the mouse to place it correctly, it leaps out of the way - just like a spoof game or an annoying virus (except as far as I know the machine is clean).  It works properly under IE8 (garlic!).  The uncontrolled scrolling also occurs: this requires the mouse to reach the top edge of the map, and then there is no way to stop it.  The only way then is to close the tab, no other escape.  If I do not try to reach the marker, but grab the map with L-mouse-down, the cursor disappears right of the left-most edge of the edit icons (and then stays invisible), the marker still jumps, but now I get a pop-up box "Click to place me on the map", which will not go away.  In fact, if I now say "Done", the cursor stays invisible, the marker still jumps if I get close to it (by trial and error).
Hoping the fix is forthcoming.  I shall not be updating my other machines until.

Comment 12

6 years ago
(In reply to comment #11)
@Dr Darvell, that is bug 540491.  The fix should be live in Google Maps by the end of the week if all goes well.

Comment 13

6 years ago
OK, thanks - look forward to it.

Comment 14

6 years ago
Chip, is this one fixed as well?

Comment 15

6 years ago
Seems to be OK for me.
Thanks all.

Comment 16

6 years ago
Yes Neil. And thanks for all your analysis on these, which was spot on. I should have given you kudos in my comments on the other bug.

Comment 17

6 years ago
OK thanks for the fix!
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.