Closed Bug 390621 Opened 17 years ago Closed 16 years ago

Cannot right click second time on bookmarks menu

Categories

(Firefox :: Bookmarks & History, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 404766

People

(Reporter: martijn.martijn, Unassigned)

Details

To reproduce: - Open bookmarks menu - Right click on a bookmark to open context menu - Right click on another bookmark to open context menu for that bookmark Actual result: The last step doesn't work, no context menu is opened for that bookmark Expected result: Context menu for that bookmark should have opened, the relevant bookmark menu-item should become highlighted.
OS: Windows XP → All
Related bugs: bug 389542 (although that's apparently a Mac-only widget issue), bug 389344 (perhaps the same issue as bug 389542).
Component: Menus → Places
QA Contact: menus → places
Martijn: I'm assuming that you're using Windows, if that isn't the case I suppose this is a dupe :)
Gavin: It also happens with Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a8pre) Gecko/2007080404 Minefield/3.0a8pre. Also for the contents of a folder on the Bookmarks toolbar.
Well, now the bookmarks menu closes on the second right click. I'll mark this as a duplicate of bug 404766, because it's now basically the same as this bug.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
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.