Closed Bug 417704 Opened 12 years ago Closed 11 years ago

Clicking wyciwyg item in bookmarks sidebar breaks sidebar context menu


(Firefox :: Bookmarks & History, defect)

Windows XP
Not set





(Reporter: mcdavis941.bugs, Unassigned)



User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv: Gecko/20080201 Firefox/
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3) Gecko/2008020514 Firefox/3.0b3

For whatever reason, I ended up with a wyciwyg item under Unfiled Bookmarks.  If you left-click this item, nothing happens, and from then on any right-clicks on items in the bookmarks sidebar bring up a context menu with all menuitems disabled.  This continues no matter which item you right-click on until you left-click a different unfiled bookmark, and from then on the context menu starts working again.

The item is wyciwyg://0/

Probably a separate issue as to whether wyciwyg items should be present in the Unfiled Bookmarks list.

Reproducible: Always

Steps to Reproduce:
1.  Start with a wyciwyg item under Unfiled Bookmarks (no idea how)
2.  Click (left-click, to open) that item in the Bookmarks sidebar
3.  Right-click any item under Unfiled Bookmarks
Version: unspecified → Trunk
bug 420331 does not allow wyciwyg uris to be added to history
Closed: 11 years ago
Depends on: 420331
Resolution: --- → WORKSFORME
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.

Component: Places → Bookmarks & History
QA Contact: places → bookmarks
You need to log in before you can comment on or make changes to this bug.