Is this still an issue ?
(In reply to Matthias Versen [:Matti] from comment #2) > Is this still an issue ? Yes, it is still an issue.
Component: General → Plug-ins
Product: Firefox → Core
Version: 3.5 Branch → unspecified
(In reply to Siarhei from comment #0) > The applet is destroyed after style of the div is changed to "display: none". > > I don't think an applet should be destroyed in the case. It still exists on > a page. Right, the whatwg spec says that applet should be unaffected by the display property: http://www.whatwg.org/specs/web-apps/current-work/multipage/obsolete.html#the-applet-element Note that you should be using object or embed tags instead if at all possible, which are supposed to be stopped when going display:none.
I don't think we treat applet different from object/embed in this regard, and the behavior of stopping the plugin when it becomes display:none is required by web compat with other existing content. I think that unless there is a specific reason why Hixie made <applet> different from object/embed in the spec, we should try to get the spec changed and WONTFIX this bug. gfritzsche, can you research and post to firstname.lastname@example.org if appropriate?
6 years ago
Assignee: nobody → georg.fritzsche
Note that we broke some situations of stopping display:none plugins that are already running, but this is unintentional and will be fixed in bug 788900
(In reply to John Schoenick [:johns] from comment #6) > Note that we broke some situations of stopping display:none plugins that are > already running, but this is unintentional and will be fixed in bug 788900 Sorry, bug 784131
5 years ago
Priority: -- → P3
4 years ago
Assignee: georg.fritzsche → nobody
I'm marking this bug as WONTFIX per bug #1269807. For more information see - https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.