Closed
Bug 199033
Opened 22 years ago
Closed 22 years ago
Remove full-page plugin code in GlobalWindowImpl::SetNewDocument()
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
People
(Reporter: jst, Unassigned)
Details
Attachments
(1 file)
|
(deleted),
patch
|
peterlubczynski-bugs
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
A while back we added code to GlobalWindowImpl::SetNewDocument() to ensure that
the JS scope was cleared when leaving a full-page plugin document, that's no
longer needed now that there's always a document in the full-page plugin case too.
|
Reporter | |
Comment 1•22 years ago
|
||
|
|
Reporter | |
Updated•22 years ago
|
Attachment #118348 -
Flags: superreview?(bzbarsky)
Attachment #118348 -
Flags: review?(peterlubczynski)
|
||
Comment 2•22 years ago
|
||
Comment on attachment 118348 [details] [diff] [review]
Remove the full-page plugin specific code.
r=peterl (the fun of removing all these hacks begins!)
Attachment #118348 -
Flags: review?(peterlubczynski) → review+
|
||
Comment 3•22 years ago
|
||
Comment on attachment 118348 [details] [diff] [review]
Remove the full-page plugin specific code.
sr=bzbarsky. Can we land this for 1.4a so as to catch any "issues"? ;)
Attachment #118348 -
Flags: superreview?(bzbarsky) → superreview+
|
|
Reporter | |
Comment 4•22 years ago
|
||
Landed. FIXED.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
|
||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•