267173 - Mac OS X cookie set request sheet should not inhibit other windows from browsing

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Dave Chand]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20041031 Firefox/1.0RC2
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.3) Gecko/20041031 Firefox/1.0RC2

Sometime when I am browsing with multiple windows open, a window in the
background will ask to set a cookie, but since it is in a window in the
background I am not aware of it, but the foreground window halts for what seems
like an unknown reason. I would like for when a website that is being browsed in
a background window is requesting to set a cookie, the windows in the foreground
continue to operate. Also if a website in a tab is requesting a cookie, the
cookie request sheet should only popup when that tab is selected not before. 

Bottomline a cookie request in one tab/windows should not inhibit browsing on
other windows

Reproducible: Always
Steps to Reproduce:
1.Clear all of your cookies.
2.open a site that takes a while to load and want to set a cookie in one window
3. open a new window and browse normally,
4. when the site in the background is ready to set its cookie, the browsing
sessions halts.

Actual Results:  
firefox freezes until the cookie set request sheet gets an input

Expected Results:  
see details above.

Comment 1

[Jo Hermans]

Myabe a dupe of bug 257546. But the bigger problem is that a sheet is supposed
to be modal for its document (that's why it's attached to the window). But this
doesn't work very well with tabs.

Comment 2

[Arthur Wiebe]

Works for me:
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050325
Firefox/1.0+

Comment 3

[Gervase Markham [:gerv]]

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/

Comment 4

[Gervase Markham [:gerv]]

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.