Closed Bug 632884 Opened 14 years ago Closed 14 years ago

Google My Maps can't drag and drop a pin

Categories

(Firefox :: General, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 540491
Firefox 4.0b11

People

(Reporter: camd, Unassigned)

References

()

Details

(Keywords: regression)

Attachments

(3 files)

In Google My Maps, you can create custom maps with pin locations to share. Steps: Go to maps.google.com Login to google Click the "My Maps" link next to "Get Directions" Click "Create New Map" In the upper left of the map area, there are 3 icons. A hand, a Pin, and a Route. Click the Pin. Exp: the new Pin should follow your mouse Act: it sticks where you clicked the icon, but doesn't follow your mouse. Clicking a location does nothing. Attempting to click the pin that you can see behind the Pin Button will often put you into a "scrolling up indefinitely" mode. Tried in Chrome and it works as I'd expect. Tried setting general.useragent.extra.browser to "Firefox" (as mentioned in bug 504530) and it didn't help.
OS: Mac OS X → All
Component: Drag and Drop → General
Product: Core → Firefox
QA Contact: drag-drop → general
Target Milestone: --- → Firefox 4.0b11
Is this a regression from 3.6?
Looking for regression range. Works as expected in Firefox 3.6.13
Keywords: regression
A range would be excellent.
blocking2.0: --- → ?
Hmm, this fails in Beta1. When I click on the "My Maps" link, I see a yellow bar at the top saying: "Additional plugins are required to display all the media on this page" So that's probably related...
blocking2.0: ? → ---
In Alpha 1 and Alpha 5, I get "Unresponsive Script" error when I click the My Maps link.
(In reply to comment #7) Disregard that. That one is about Printing. (In reply to comment #6) > Created attachment 511160 [details] > Unresponsive script screenshot Is there any related Error Console Output?
None in the latest Minefield. But in the Alpha 5, I got the attached log error.
Attached image Alpha 5 error log
Attached image Beta 11 error log
This is what I saw with Beta 11 in the error log.
still happens on FF4 final
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: