Full-page plug-ins get destroyed with display:none on IFRAMEs

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
16 years ago
6 years ago

People

(Reporter: peterlubczynski-bugs, Assigned: peterl-bugs)

Tracking

Trunk
mozilla1.4beta
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [PL2:NA], URL)

(Reporter)

Description

16 years ago
The fix to bug 173938 introduced some hacky code to destroy full-page plugins
embedded in an IFRAME before the frame is destroyed because a plugin's window
frame must be destroyed before its parent. This bug is about removing that code
so that display:none on a full-page plugin will cause it to hide rather than
being destroyed.
(Reporter)

Updated

16 years ago
Whiteboard: [PL2:NA]
Target Milestone: --- → mozilla1.4beta
Is the idea here to move the relevant code out of the plugin frame and into the
content model?
(Reporter)

Comment 2

16 years ago
Yes, this bug should be fixed as a side-effect of these two:

- bug 90268 is about moving embedded plugin lifetime to content
- bug 90256 is about full-page plugins being part of the DOM by reusing the
embedded code path

Updated

16 years ago
Summary: full-page plugins get destoryed with display: none in IFRAMES → Full-page plug-ins get destroyed with display:none on IFRAMEs
QA Contact: shrir → plugins

Updated

6 years ago
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.