Sounds good, but then it will always use the infobar. Are they fundamentally unable to fire at a particular <object>?
Or could we receive the event at the window level and search the DOM tree for plugins of that type and then display the overlay on them? ----- Original Message ----- From: "Benjamin Smedberg" <[email protected]> To: "Felipe Gomes" <[email protected]>, "Eric Rescorla" <[email protected]> Cc: [email protected], "Georg Fritzsche" <[email protected]> Sent: Tuesday, July 15, 2014 5:49:11 PM Subject: Re: GMP crash reporting update (schedule slip likely) On 7/15/2014 4:41 PM, Felipe Gomes wrote: > Ideally, on a crash, the plugin code should send a PluginCrashed event, one > per plugin instance, which is how it's done for the NPAPI plugins. Do these > new plugins use nsPluginHost et. al.? No. They don't use nsPluginHost and they don't use nsObjectLoadingContent. However, we can still fire an event at the DOM window or document. That event can have the same properties that a NPAPI plugin crashed event has: pluginName/pluginDumpID. The only thing that's different is that because the event is fired directly at the window instead of at a particular <object> element, the code which currently tries to display the plugin crash in the element will need to short-circuit all the way to the hidden-plugin case at http://mxr.mozilla.org/mozilla-central/source/browser/base/content/browser-plugins.js#1268 --BDS _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
