Closed Bug 770978 Opened 13 years ago Closed 12 years ago

Cookie dialog hangs with particular site (runnersworld.com)

Categories

(Firefox :: Settings UI, defect)

13 Branch
x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 430006

People

(Reporter: contact, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:13.0) Gecko/20100101 Firefox/13.0.1 Build ID: 20120614114901 Steps to reproduce: Go to http://www.runnersworld.com/community/forums/shoes-stuff/shoes/asics-gel-kayano-18-review with cookie setting: "ask me every time". Actual results: After four or five dialogs for cookies (which I all reject), a dialog for confirmation of cookies just gets stuck -- nothing happens any more, no matter which button is pressed. Can only kill firefox and restart. Expected results: The dialog should be responsive and respect my button clicks.
I may add a cause for this problem: while the cookie dialogs are spawnings in rapid succession, an "older" one is positioned on top of a "newer" one. As only the last spawned cookie dialog can be clicked/accepted/rejected (it's modal, after all), you can't touch the older one and the newer one will be unreachable. Example: We have 5 cookie dialogs (CDLG0 to CDLG4), spawning in rapid succession. Normally, you'd expect this order: CDLG0 - CDLG1 - CDLG2 - CDLG3 - CDLG4 ^---<---^ ^---<---^ ^---<---^ ^---<---^ The lines are marking modal blocking (CDLG1 is blocking CDLG0, CDLG2 is blocking CDLG1 and *subsequently* CDLG0, etc ...) In this scenario, you can get rid of CDLG4 first, then CDLG3, then CDLG2, then CDLG1 and lastly CDLG0. Now, due to some weird race condition, this order may occur: CDLG0 - CDLG1 - CDLG2 - CDLG4 - CDLG3 ^-------<-------^ ^--->---^ ^---<---^ ^---<---^ CDLG3 opens *after* CDLG4. However, as CDLG4 is blocking CDLG3, you can't just click on any button in CDLG3, thus breaking the chain and the only way to get rid of the situation is to kill Firefox. Hope I was able to shed some light on the issue. Oh, yeah, of course I have seen this problem, too. OS X 10.6.8 here.
Another incarnation of this problem is bug #817369 - though at least it won't make the Firefox window unusable, as Escape is still working for him. Still seeing it with Firefox 21 on Mac OS X 10.8.3.
comment #0 seems to be about how it looks (bug 430006, marking duplicate), comment #1 is bug 420155.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Component: Untriaged → Preferences
Resolution: --- → DUPLICATE
It's ridiculous this bug has persisted for nearly a decade. I actually STOPPED using Firefox two years ago because I got tired of this bug on my Mac. I now use Chrome as my only web browser. This is ridiculous. It's a shame, because I really really really wanted to support Mozilla, but this bug rendered the browser totally unusable on my Mac.
You need to log in before you can comment on or make changes to this bug.