from asking to reload and/or offer to do the plugin update check). I say for simplicity sake, any notification should just offer either a way to suggest a workaround because of the problem or offer to solve the problem (ie. I don't think there really is a need to tell the user how many tabs are actually affected. I don't think many non techie users would understand otherwise unless the browser offers to 'reload all affected tab(s)' for them. While I see the significance of knowing how many tabs, its just as easy to globally inform the user that 'plugin x crashed' and the user could 'try reloading all tab(s) running plugin x'. Just for conversation sake here, what does chrome do?ĭon't forget its just as easy to right click the tab bar and select reload all tabs instead of doing so manually, or in the case stated, the user would see a need to reload individual tabs that broke down or maybe the browser could track the crashed tabs as suggested and offer to 'reload all affected tab(s)' rather than all tabs which use that plugin but didn't crash or all the browser tabs using the tabbar option. > just because the page would need to be manually refreshed when we technically > time and bandwidth for both the user and site (due to the following comment) > to manually refresh each and every single tab. > number of tabs that had the crashed plugin loaded. > I just think it would be annoying to dismiss the notification bar N times for N > but for sites that don't have the plugins autoplay, this makes sense. > of them to watch one at a time now having all tabs videos start playing again
> users who may have opened a dozen tabs of youtube videos and paused all but one > That is what I would personally like but then again we'd run into the issue of Bug 391725 should be WONTFIXed then even though I disagree. Make a little sense to me even though I don't understand exactly what you mean but I get the jist of it.
> about the plugin state which will no longer be correct. > We don't want to refresh in-place because page script often makes assumptions Just for conversation sake here, what does chrome do? This is turn wastes the users time and bandwidth for both the user and site (due to the following comment) just because the page would need to be manually refreshed when we technically don't have to. The users would then have to manually refresh each and every single tab. I just think it would be annoying to dismiss the notification bar N times for N number of tabs that had the crashed plugin loaded. That is what I would personally like but then again we'd run into the issue of users who may have opened a dozen tabs of youtube videos and paused all but one of them to watch one at a time now having all tabs videos start playing again but for sites that don't have the plugins autoplay, this makes sense. > Kurt, what would the effect of dismissing that notification be? to refresh all Note that bug 525849 covers UI for submitting crash reports for the crashed plugin. If not, we should drop down the doorhanger.
* If the plugin notification can be displayed directly within the plugin frame, ** is the plugin large enough to display a notification directly within it * Any subsequent times the plugin crashes, we should check to see * If the user reloads in any way (doorhanger, toolbar, or Ctrl-R), we should * The doorhanger should have a checkbox, on by default, for submitting theĬrash report, and a text, something like "Adobe Flash has crashed." and a * The first time a plugin crashes, we should drop down a doorhanger. As such, we need to add browser and content UI to handle when this happens so the user knows what's going on.įrom bug 519541 comment 5 - limi made some preliminary suggestions for what this UI should be: With out-of-process-plugins, plugins can now crash without taking down the entire browser. +++ This bug was initially created as a clone of Bug #519541 +++