Closed
Bug 470356
Opened 16 years ago
Closed 16 years ago
Cookie dialogs pop with center=screen instead of center=owner
Categories
(Core :: Networking: Cookies, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: mozilla, Assigned: mozilla+ben)
References
Details
(Keywords: fixed1.9.1)
Attachments
(2 files, 1 obsolete file)
2.10 KB,
patch
|
dwitte
:
review+
|
Details | Diff | Splinter Review |
2.38 KB,
patch
|
mozilla+ben
:
review+
jst
:
superreview+
jst
:
approval1.9.1+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5
This may be related to 405239.
With 3.0.5, dialogs about cookie handling pop in the "center" of the Windows "screen" (which is taken as the main monitor) instead of the center of the Firefox window. This is extremely irritating for those of us who run FF on a big second monitor, where it belongs.
Reproducible: Always
Steps to Reproduce:
1. Put Firefox on a second monitor.
2. Visit a site that causes a cookie dialog.
Actual Results:
Dialog pops in middle of main monitor.
Expected Results:
Dialog should pop in middle of window containing the visited site.
Comment 1•16 years ago
|
||
jst, could this be a regression from bug 405239?
Comment 3•16 years ago
|
||
This should really block 3.1 I think.
Blocks: 405239
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking-firefox3.1?
Version: unspecified → Trunk
Updated•16 years ago
|
Component: General → Networking: Cookies
Flags: blocking-firefox3.1?
Product: Firefox → Core
QA Contact: general → networking.cookies
Comment 4•16 years ago
|
||
Restoring the blocking nomination lost by the component move...
Flags: blocking1.9.1?
Assignee | ||
Comment 6•16 years ago
|
||
With this patch, the cookie dialog is modal for the root chrome window rather than the tab containing the permission-requesting page. This removes the confusion about which monitor is displaying the dialog, but also avoids unwanted tab switches.
I'm not testing that the root window is actually a chrome window, or that the root window is actually different from the provided parent window, but it seems safe to say the root will always be a chrome window. If there's any problem getting the root window, |parent| will just be null, so at worst this patch degenerates to the present behavior.
Attachment #358083 -
Flags: superreview?(jst)
Attachment #358083 -
Flags: review?
Assignee | ||
Updated•16 years ago
|
Attachment #358083 -
Flags: review? → review?(dwitte)
Comment 7•16 years ago
|
||
Comment on attachment 358083 [details] [diff] [review]
parenting dialog with chrome window instead of tab
> // Given the nature of this dialog and the frequency of it popping
> // up for those few users that have it enabled we do not want this
> // dialog to be parented at a window. Pass in nsnull as the
> // parent. See bug 405239 for more details.
r=me, but this comment is no longer correct. can you update it to mention the new parenting and this bug#?
thanks for the patch!
Attachment #358083 -
Flags: review?(dwitte) → review+
Assignee | ||
Comment 8•16 years ago
|
||
Assignee | ||
Updated•16 years ago
|
Attachment #358097 -
Attachment is obsolete: true
Assignee | ||
Comment 9•16 years ago
|
||
Assignee | ||
Updated•16 years ago
|
Attachment #358108 -
Attachment is patch: true
Attachment #358108 -
Attachment mime type: application/octet-stream → text/plain
Attachment #358108 -
Flags: superreview?(jst)
Attachment #358108 -
Flags: review?(bnewman)
Assignee | ||
Updated•16 years ago
|
Attachment #358108 -
Flags: review?(bnewman) → review+
Updated•16 years ago
|
Attachment #358108 -
Flags: superreview?(jst)
Attachment #358108 -
Flags: superreview+
Attachment #358108 -
Flags: approval1.9.1+
Comment 10•16 years ago
|
||
Comment on attachment 358108 [details] [diff] [review]
updated comment without the random trash (sorry)
sr=jst. I don't think I can claim that this is a blocker, but I think we should take this change for 1.9.1 nonetheless. Approving.
Updated•16 years ago
|
Flags: blocking1.9.1? → blocking1.9.1-
Updated•16 years ago
|
Assignee: nobody → bnewman
Comment 11•16 years ago
|
||
Fixed for trunk and 1.9.1.
Blocks: 471640
Updated•16 years ago
|
Attachment #358083 -
Flags: superreview?(jst)
Updated•16 years ago
|
Blocks: multimon-win
Comment 13•15 years ago
|
||
I have trouble following the bug fixing process in Firefox. Is this bug - and any related bugs - now fixed in 3.5? (My understanding is that even though it is marked as fixed, it wasn't fixed in 3.0.11 - it was waiting for a "major" release).
Thanks.
Comment 14•15 years ago
|
||
Yep, it's marked as "fixed1.9.1". Gecko 1.9.1 corresponds to Firefox 3.5.
You need to log in
before you can comment on or make changes to this bug.
Description
•