Closed
Bug 451364
Opened 17 years ago
Closed 17 years ago
Popup menu in bookmarks sidebar disabled during first page loading
Categories
(Firefox :: Bookmarks & History, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: rpmdisguise-nave, Unassigned)
References
Details
With the bookmarks sidebar open, just after opening Firefox, if you click on a bookmark to replace the home page and then try to right-click on another bookmark while the first bookmark hasn't finished loading, the popup menu on the second boomark has all its options disabled. If you wait until the page corresponding to the first clicked boomark has finished, popup menu appears normally, as it happens if you try to repeat the process with a third boomark while the second is loading.
Tested on Firefox 3.0.1 es-ES Linux, Firefox 3.0.1 en-US Windows and Firefox 3.0.2pre es-ES Linux nightly.
Steps to reproduce:
1. Open Firefox 3.0.x (not tested with 2.0.0.x).
2. Open bookmarks sidebar.
3. Expand boomarks tree until you can directly access to at least two boomarks.
4. Left click on the first boomark so it replaces the current (hidden or not) tab content.
5. While the first bookmark page is still loading, right-click in the second boomark to try to choose "Open in a new tab". All options in the pop-up menu will be disabled.
Expected results:
At least some options in the pop-up menu should be enabled, just like it happens when doing the same operation with a second and third bookmark.
Comment 1•17 years ago
|
||
This regressed back on 5-18-2007 which is when places-bookmarks was enabled. The respin right after enabling is the first showing this problem.
| Reporter | ||
Comment 3•17 years ago
|
||
This bug seems no to be present in Firefox 3.0.8 anymore.
Comment 4•17 years ago
|
||
Confirmed
-> WFM
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Comment 5•17 years ago
|
||
Ok, but bug https://bugzilla.mozilla.org/show_bug.cgi?id=485358 that supposedly is duplicate of this bug, is still reproducible and not fixed.
Comment 7•16 years ago
|
||
This was fixed by the patch for bug 488846.
Depends on: 488846
Resolution: WORKSFORME → FIXED
Comment 9•16 years ago
|
||
Okay, this really was fixed by the patch for bug 488846. I can reproduce this bug in the Fx3.0.8 and Fx3.0.11, so I'm a bit puzzled by two people saying that it was fixed in 3.0.8.
Depends on: 488846
Resolution: WORKSFORME → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•