643160 - Incorrect position of unresponsive script dialog with multiple monitors

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Rowan Kerr]

User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0

With a multiple monitor configuration in OS X (10.6.6) (two displays, secondary left of primary), the unresponsive script dialog pops up centered between the boundary of the two displays and slightly off the top of the display.

Reproducible: Didn't try

Steps to Reproduce:
1. Configure 2 monitors in OS X. Arrange display without menu bar on the left.
2. Visit a site with slow javascript or otherwise trigger the "unresponsive script" dialog.
3. Notice the position of dialog is not where it should be.
Actual Results:  
Dialog appears with x-position such that is spans the two displays and y-position above the top of the display.

Expected Results:  
Dialog should have appeared inside Firefox attached to the appropriate tabbed window and centered horizontally relative to it.

Comment 1

[Rowan Kerr]

Attachment: Screenshot of misplaced dialog.

Comment 2

[Wayne Mery (:wsmwk)]

dup of bug 643867?

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+1]]

(In reply to comment #2)
> dup of bug 643867?

Not sure. I will CC Markus.

Comment 4

[Rowan Kerr]

Not a dupe. This issue is about the placement of the dialog between displays and not even attached to a Firefox window. Possibly related though.

I haven't been able to repro this issue by triggering the unresponsive dialog from a web page. (Though trying to do that made me notice bug 643867). It may only happen when an internal js is running slowly.

resource://gre/components/nsUrlClassifierLib.js is what triggered the placement outside of a Firefox window for me.

Comment 5

[zakwilcox+mozillabugzilla]

Perhaps take a look at bug 575929 too when fixing this.

Comment 6

[Wayne Mery (:wsmwk)]

Frankie, can you reproduce this and/or bug 575929?

Comment 7

[Frankie]

Could someone provide a URL that reliably triggers the unresponsive script dialog?

Comment 8

[Wayne Mery (:wsmwk)]

Bug 640742 has a URL that might trigger it for you (it didn't for me, but the OP indicates it did)

Comment 9

[zakwilcox+mozillabugzilla]

I've found bug 482811 a disappointingly reliable way to elicit the unresponsive script thingy.

Comment 10

[Frankie]

bug 640742 URL doesn't give me a problem.
bug 482811 is for T-bird.
I searched Bugzilla for "unresponsive script", tried a couple URLs, but none of them are giving me the dialog.
Anyone know a testcase script?

Comment 11

[zakwilcox+mozillabugzilla]

> bug 482811 is for T-bird.

It's in a shared component, hence comment #34 --- or see its twin in 476541 if you really don't trust me :)

Comment 12

[WBT]

Attachment: Screenshot of misplaced dialog- second user example

I also have multiple monitors on Mac 10.6.8, FF 4.0.1.  I have two monitors, the left one shorter than the right, and the menu bar on the right monitor. 
Unresponsive script alerts appear in the top center, so that only a part of the dialog is visible.  Thankfully, it's the portion with buttons, and after I while I go to look for dialogs there, but sometimes it takes 15 min. or more.  
This is very odd behavior.

Comment 13

[WBT]

To trigger the unresponsive script dialog, visit http://kb.mozillazine.org/Unresponsive_Script_Warning, or look at a failed extension that gave this error, or maybe write a simple script that doesn't respond for a while.  Reducing dom.max_script_run_time in about:config will trigger it more often.

Comment 14

[Wayne Mery (:wsmwk)]

(In reply to WBT from comment #13)
> To trigger the unresponsive script dialog, visit
> http://kb.mozillazine.org/Unresponsive_Script_Warning, or look at a failed
> extension that gave this error, or maybe write a simple script that doesn't
> respond for a while.  Reducing dom.max_script_run_time in about:config will
> trigger it more often.

Comment 15

[Frankie]

Unfortunately, the unresponsive extensions list on that page is old. All of the ones I checked are either updated or no longer exist.

The testcase in Bug 476541 does not trigger a dialog, even when I set all of the about:config run time options to 1 second.

Also, step 1 "Arrange display without menu bar on the left" is no longer possible, because newer versions of OS X put a separate menu bar at the top of each display.

Nevertheless, if someone can point me to a testcase URL that reliably triggers the error dialog, I'll try it.

Comment 16

[Frankie]

Followup: I finally got a few pages to run scripts longer than a second. 
The error dialog displayed correctly in many combinations of monitor and window positions.
WFM in FFDE 44.0a2 on OS X 10.10

Comment 17

[Wayne Mery (:wsmwk)]

(In reply to Frankie from comment #16)
> ...
> WFM in FFDE 44.0a2 on OS X 10.10

Rowan, do you agree this works?

Comment 18

[Phoenix]

Resolved per whiteboard