if opening two external links and one requires accepting or rejecting of cookies, the cookies dialog is unresponsive

RESOLVED EXPIRED

Status

()

Firefox
Tabbed Browser
--
critical
RESOLVED EXPIRED
13 years ago
13 years ago

People

(Reporter: Gary Elshaw, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-au) AppleWebKit/312.1 (KHTML, like Gecko) Safari/312
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050502 Firefox/1.0+ Mnenhy/0.7.2.0

When opening two external links in the background and the site needs a response to accept or reject 
cookies, the cookies dialog is unresponsive causing the user to force quit. This is often happening 
while using an rss reader, opening a link in the background with another soon following it then 
bringing Firefox to the foreground. There is no way to focus the individual pages and the cookies 
dialog is unreponsive forcing a force quit

Reproducible: Always

Steps to Reproduce:
1. have firefox settings to always ask about cookies
2. open external link to a site you have never been to asking firefox to open it in the background via rss 
reader
3. repeat step two
4. Bringing Firefox to the front, the cookies dialog should be unresponsive

Actual Results:  
user has to force quit Firefox

Expected Results:  
allowed the user to accept or reject cookie
*** Bug 295875 has been marked as a duplicate of this bug. ***
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.