559375 - OOPP: Difficulty reloading page when Quicktime Plugin crashes

Status: RESOLVED WONTFIX

(Core Graveyard :: Plug-ins, defect)

Description

[Marcia Knous [:marcia]]

Seen while running Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.4) Gecko/20100413 Firefox/3.6.4 (.NET CLR 3.5.30729)

STR:
1. Visit the URL.
2. Kill the plugin container process.
3. Get the Plugin Crashed UI.
4. Try to reload the page.

On the first occasion that I tried this the whole browser crashed with no crash report. On subsequent attempts the browser did not crash but the "Reload this page" link doesn't work right away and I cannot reload the page using the button in the toolbar. It is as if the browser is temporarily frozen. Eventually the mouse click that I initiated to reload the page will happen but not right away.

QT version is 7.6.6.

Comment 1

[juan becerra [:juanb]]

There seems to be an overlay that prevents you from clicking on the elements of the crashed-plugin UI. The "?" doesn't work either.

Comment 2

[Benjamin Smedberg]

If this is just the web page putting stuff on top of the plugin, we can either WONTIFX it, or we can try to detect it and show the notification bar in this case. Is there some way layout can let us ask whether an element is being overlayed?

Comment 3

[Robert O'Callahan (:roc) (email my personal email if necessary)]

You could use the new nodesFromRect API to detect whether there's anything over your plugin UI.

Comment 4

[Justin Dolske [:Dolske]]

I think this is WONTFIX -- the page has a video control overlay <div> on top of the plugin. Seems to be triggered by mouseover, so we might not even be possible to detect the issue until the user tries to click something. Not much we can do about this.

Comment 5

[Mike Beltzner [:beltzner, not reading bugmail]]

I'm not sure I agree with this WONTFIX; comment 3 indicates that we can detect this case, and the fact that this is the UI on Apple's trailers page means that it's a commonly viewed webpage.

Basically from what I understand, we're saying that we're OK with users not being able to interact with the "oopsie" UI on a pretty popular webpage. That seems not-OK to me.

Comment 6

[Benjamin Smedberg]

I re-propose always showing the notification bar, and keeping it up even after page refresh as a way of nagging users to submit their crash report...

Comment 7

[Mike Beltzner [:beltzner, not reading bugmail]]

Benjamin: can you file a separate bug for that? Let's not scope creep this beyond the immediate problem.