Closed Bug 380301 Opened 18 years ago Closed 17 years ago

unable to dnd file links (as bookmarks) under the "Bookmarks" menu

Categories

(Firefox :: Bookmarks & History, defect, P4)

x86
Windows XP
defect

Tracking

()

VERIFIED DUPLICATE of bug 337761
Firefox 3 beta3

People

(Reporter: moco, Assigned: stevewon)

References

Details

(Keywords: regression, Whiteboard: [Fx2-parity])

Attachments

(1 file)

unable to dnd file links (as bookmarks) under the "Boomarks" menu in fx 2, on windows, you could drag a link over the Bookmarks menu and it would open up, allowing you to file where you want (and if you hover over a subfolder, that would open up). on trunk with places bookmarks, this doesn't work anymore.
Flags: blocking-firefox3?
Keywords: regression
Whiteboard: [Fx2-parity]
i see slightly different result: when i drag link over the bookmark menu it doesn't open when i drop the link over the bookmark menu, the menu popup for a split second and new bookmark was added in the bottom of the last used\opened folder.
I see the same thing as onemen.one.
Summary: unable to dnd file links (as bookmarks) under the "Boomarks" menu → unable to dnd file links (as bookmarks) under the "Bookmarks" menu
Flags: blocking-firefox3? → blocking-firefox3+
Target Milestone: --- → Firefox 3 alpha6
finding owners for all the A6 blockers. can you please put a swag in the whiteboard? then we can review and load-balance at the next places meeting.
Assignee: nobody → swon
Whiteboard: [Fx2-parity] → [Fx2-parity], 3d
Whiteboard: [Fx2-parity], 3d → [Fx2-parity], [swag: 3d]
So it seems like the problem is that the timer to bring up a bookmarks menu list initialized on drag enter, but not fired until the mouse click is released. Same goes for the timer with closing the menu list. Everything works fine if we just show the popup menu list immediately instead of using the timer to do so with a slight delay. Would anything be preventing nsITimer.initWithCallback from firing before a click is released? (Not sure if nsITimer always works like that or not). Any feedback would be helpful. Thanks.
So it seems like the problem is that the timer to bring up a bookmarks menu list is initialized on drag enter, but not fired until the drag is released. Same goes for the timer with closing the menu list. Everything works fine if we just show the popup menu list immediately instead of using the timer to do so with a slight delay. Would anything be preventing nsITimer.initWithCallback from firing before a drag is released? (Not sure if nsITimer always works like that or not). Any feedback would be helpful. Thanks.
This patch shows the timer function & function calls I mentioned.
Er, not really a patch.
So I asked around, and this seems to be a problem with Windows. If I understand correctly...nsITimer fires after the mouse release, because drag-n-drop code needs to run in its own event loop which doesn't allow timers to fire.
retargeting bugs that don't meet the alpha release-blocker criteria at http://wiki.mozilla.org/Firefox3/Schedule.
Target Milestone: Firefox 3 alpha6 → Firefox 3 beta1
neil, can you help out with this? (do you think it might be more fall out from the nsIThreadManager change, bug #326273?)
Yes, and it's the same cause as bug 337761.
Depends on: 337761
Whiteboard: [Fx2-parity], [swag: 3d] → [Fx2-parity]
Status: NEW → ASSIGNED
Target Milestone: Firefox 3 M7 → Firefox 3 M8
Target Milestone: Firefox 3 M8 → Firefox 3 M9
This does not need to block M9.
Target Milestone: Firefox 3 M9 → Firefox 3 M10
Target Milestone: Firefox 3 M10 → Firefox 3 Mx
Target Milestone: Firefox 3 Mx → Firefox 3 M11
Priority: -- → P4
Not going to continue to block on this. If you disagree with this decision, please renominate with reasons why we can't ship with this in final
Flags: wanted-firefox3+
Flags: blocking-firefox3-
Flags: blocking-firefox3+
Renominating for blocking. Reason is the same as in Bug 389290: "Because it was fully functional in 2.0 and because it is a basic UI design requirement. It looks really bad to regress something like this between final version implementations. It is almost a requirement when moving bookmarks around that you can see where they are going to be dropped. Otherwise, the UI feels very disconcerting. You can still do it, but it is very unprofessional, and takes away some speed and accuracy from the user."
Flags: blocking-firefox3- → blocking-firefox3?
Flags: blocking-firefox3? → blocking-firefox3-
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
No longer depends on: 337761
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h". In Thunderbird 3.0b, you do that as follows: Tools | Message Filters Make sure the correct account is selected. Click "New" Conditions: Body contains places-to-b-and-h Change the action to "Delete Message". Select "Manually Run" from the dropdown at the top. Click OK. Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter. Gerv
Component: Places → Bookmarks & History
QA Contact: places → bookmarks
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: