User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041016 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041016 Firefox/1.0 Must click twice to close a Bookmark Toolbar folder after dropping a bookmark on top of a folder inside of it. Reproducible: Always Steps to Reproduce: 1. Drop a bookmark from the root of a Bookmark Toolbar folder (or from another Toolbar folder) on top of a folder within it. 2. Move the mouse up to the depressed folder button fast enough as to not activate another folder inside of it. 3. Click once to close it. Actual Results: The Toolbar folder doesn't close. Click it again to close it. Expected Results: The Toolbar folder should have closed after the first click. You can also reproduce this if you drop a bookmark somewhere inside the folder (instead of dropping it on top of it), as long as you then move the mouse below the root dropdown menu and then directly up it to the Toolbar button. If you instead follow the hierarchy backwards in the correct order, you will not see the bug. This bug is minor, but very annoying when rearranging bookmarks inside the Bookmark Toolbar a lot.
Note that when you drag from the Address Bar to a place within a Bookmarks Toolbar folder, or drag bookmarks from the root of the Bookmark Toolbar to a place within a Bookmarks Toolbar folder, the dropdown listing IMMEDIATELY closes. When dragging from the Bookmarks Menu to a place within a Bookmarks Toolbar folder, the dropdown listing DOES NOT close. Just FYI. I don't know if this is the preferred behavior, or if the code is just inconsistent. I would rather it be more predictable, e.g. have the dropdown ALWAYS stay open after dragging to it, until I click away.
Assignee: vladimir → vladimir+bm
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → bookmarks
This bug still exists. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061216 Minefield/3.0a1.
Status: RESOLVED → UNCONFIRMED
Resolution: EXPIRED → ---
Now that Bug 337761 has been fixed, I have noticed this buggy behavior again. Btw, this bug behavior seems to be similar to Bug 96504, except this bug only occurs when dragging already existing bookmarks within folders, and not when creating new bookmarks by dragging them from the address bar.
This bug is again temporarily not producible, because it depends on the regression of Bug 395176.
Depends on: 395176
This may also depend on, or in fact be a duplicate of Bug 225434, because the depressed bookmark/folder behavior is very similar to the results of this bug...however, I am not going to mark it as such, as I can't prove this.
I think this was, in fact, a duplicate of some other bugs, that don't seem to be present anymore. I am marking it as WFM.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago → 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.