User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:184.108.40.206) Gecko/2009032609 Firefox/3.0.8 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:220.127.116.11) Gecko/2009032609 Firefox/3.0.8 (.NET CLR 3.5.30729) I was logging bug 488434 (https://bugzilla.mozilla.org/show_bug.cgi?id=488434) and found this problem along the way. Basically, the 'sort by name' pop-up menu becomes greyed out even within the Bookmarks context menu which works in bug 488434. Reproducible: Always Steps to Reproduce: 1. Open Bookmarks context menu 2. Scramble several bookmarks by drag-and-drop it randomly within 'Bookmarks' context menu 3. Once done scrambling the bookmarks, right-click on either one of the first four Bookmarks sub-context menu (Bookmark This Page, Subscribe to This Page, Bookmark All Tabs, or Organize Bookmarks) Pay attention to 'Sort by name' options in the pop-up menu. NOTE: in case 'sort by name' works or Bookmark context menu was closed by accident, repeat the above steps once again. Actual Results: 'Sort by name' should not be greyed-out Expected Results: 'Sort by name' was greyed-out Workaround: - close the Bookmark context menu, - re-open again and right-click on either: Bookmark This Page, Subscribe to This Page, Bookmark All Tabs, or Organize Bookmarks, - choose 'Sort by Name' to sort In case 'Sort by name' does not work, it maybe related to bug 488434 (https://bugzilla.mozilla.org/show_bug.cgi?id=488434) Side notes: I frequently found user accidentally moved around the bookmark due to unknown reason. Re-sorting it back is one of the possible option to bring back from chaos ;)
Reporter, are you still seeing this issue with Firefox 3.6.10 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.