Closed Bug 436605 Opened 17 years ago Closed 17 years ago

Hangs when moving a bookmark and a (related) cookie request box appears

Categories

(Firefox :: Bookmarks & History, defect)

x86
Windows Vista
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 424900

People

(Reporter: mike, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0 Whilst moving a bookmark from one sub-folder to another using drag/drop, a dialog box comes up asking whether a cookie should be accepted or denied (my setting is 'always ask'). The cookie is related to the site whose bookmark is being moved. If this happens, neither the bookmark pane nor the dialog box have focus and nothing can be done other than shutting FF from the task manager (although the page gets properly re-drawn when other windows move over it). Restarting clears the fault, and the bookmark is not lost. Reproducible: Sometimes Steps to Reproduce: 1. Set cookies to 'ask every time'. 2. Drag a bookmark which is for a site which will want to set a cookie to a new destination (my example dragged a bookmark down about 15 lines). Actual Results: This usually causes the hang without any other action needed. Expected Results: The cookie request box should get input focus, then relinquish this focus to the main form'
This seems to be a duplicate of bug 424900. You could disable the microsummaries: Set "browser.microsummary.enabled" to false in about:config.
I have not seen it happen at all since the latest release. However, I don't see the micro summaries any more, even though I have not changed the suggested setting yet. I therefore conclude that it has been fixed in the latest release. Having read bug report 424900, I agree it is clearly a duplicate which I had not spotted.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.