1106253 - "Unresponsive Script" dialog should bring owning window to the front over fullscreen video / other windows to allow interaction

Status: UNCONFIRMED

(Core :: DOM: Core & HTML, defect)

Description

[Gert van Valkenhoef]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0
Build ID: 20141013200257

Steps to reproduce:

View full screen HTML 5 video on Ubuntu 14.04, while the system was under some load for other reasons. I also had several tabs open.


Actual results:

A "script not responding" dialog popped *under* the full screen video, and the video controls became impossible to interact with, also disabling any ability to exit full screen. I eventually solved this by alt-tabbing and/or using the "expose" functionality in unity to grab the "script not responding" dialog (which was still invisible below the full screen video) and used the keyboard to make it go away.


Expected results:

Two things could be better:

 - When a dialog that apparently blocks operation of the entire browser pops up, it would be good to exit full screen video, or make sure the dialog actually renders on top of it.

 - The dialog could be less aggressive, e.g. block only the tab that has the non-responsive script. As it is, it even grabs focus when I'm using *another* application. As a result, I can't leave firefox open when playing full screen video games (which may trigger the dialog by using up loads of cpu+ram).

Comment 1

[:Gijs (he/him)]

(In reply to Gert van Valkenhoef from comment #0)
>  - The dialog could be less aggressive, e.g. block only the tab that has the
> non-responsive script. As it is, it even grabs focus when I'm using
> *another* application. As a result, I can't leave firefox open when playing
> full screen video games (which may trigger the dialog by using up loads of
> cpu+ram).

I don't know how hard that is, but that's covered by bug 588293. I'm making this bug describe your other suggestion.

Comment 2

[Gert van Valkenhoef]

Makes sense to me! Thanks for picking this up.

Comment 3

[Wayne Mery (:wsmwk)]

(In reply to :Gijs Kruitbosch from comment #1)
> (In reply to Gert van Valkenhoef from comment #0)
> >  - The dialog could be less aggressive, e.g. block only the tab that has the
> > non-responsive script. As it is, it even grabs focus when I'm using
> > *another* application. As a result, I can't leave firefox open when playing
> > full screen video games (which may trigger the dialog by using up loads of
> > cpu+ram).
> 
> I don't know how hard that is, but that's covered by bug 588293. I'm making
> this bug describe your other suggestion.

FWIW bug 588293 was fixed 2 years ago in bug 1118618