Closed
Bug 484209
Opened 16 years ago
Closed 8 years ago
Java applet is destroyed after hiding of an element containing an aplet
Categories
(Core Graveyard :: Plug-ins, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mozilla_by, Unassigned)
Details
Attachments
(2 files)
Java applet is destroyed after hiding of an element containing an aplet.
I created an example page to show the problem.
<div id="appletDiv" style="display: block">
<applet code="InvisibleApplet.class">
</applet>
</div>
The applet div is displayed and an applet is running after loading page. 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.
Steps to reproduce:
1) complile attached InvisibleApplet.java
2) save attached index.html and put compiled applet (InvisibleApplet.class) in the same folder
3) open the page in a browser (JavaScript should be enabled)
4) click "hide applet" link
Java console will show the following trace if you enable trace and run the scenario:
basic: Starting applet teardown
stop
destroy
basic: Finished applet teardown
(In reply to Matthias Versen [:Matti] from comment #2)
> Is this still an issue ?
Yes, it is still an issue.
Flags: needinfo?(mozilla_by)
Updated•12 years ago
|
Component: General → Plug-ins
Product: Firefox → Core
Version: 3.5 Branch → unspecified
Comment 4•12 years ago
|
||
(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.
Comment 5•12 years ago
|
||
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 whatwg@whatwg.org if appropriate?
Updated•12 years ago
|
Assignee: nobody → georg.fritzsche
Comment 6•12 years ago
|
||
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
Comment 7•12 years ago
|
||
(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
Updated•12 years ago
|
Priority: -- → P3
Updated•11 years ago
|
Assignee: georg.fritzsche → nobody
Flags: firefox-backlog?
Updated•11 years ago
|
Flags: firefox-backlog? → firefox-backlog+
Comment 8•8 years ago
|
||
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
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•