Closed
Bug 946564
Opened 11 years ago
Closed 11 years ago
Make window._content chromeonly
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla29
People
(Reporter: bzbarsky, Assigned: bzbarsky)
References
Details
(Keywords: dev-doc-complete, site-compat, Whiteboard: [qa-])
Attachments
(2 files)
4.35 KB,
patch
|
peterv
:
review+
|
Details | Diff | Splinter Review |
12.18 KB,
patch
|
peterv
:
review+
|
Details | Diff | Splinter Review |
The web shouldn't use it because no one else supports it, it's been deprecated since 2001 (though without any console messages), and it's already not supported via Xrays, so extensions ought not to break.
Can we just kill it, pretty please?
Assignee | ||
Comment 1•11 years ago
|
||
> so extensions ought not to break.
Except I guess they could be getting _content on the chrome window. :( And in fact, that's exactly what they do; it's all over the addons mxr.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Assignee | ||
Comment 2•11 years ago
|
||
Actually, I'm going to try to make this chromeonly. Lack of xray support means I don't have to add it to xpidl at all, and I can hack webidl enough to allow this.
Blocks: 864845
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Summary: Can we nix window._content ? → Make window._content chromeonly
Assignee | ||
Comment 3•11 years ago
|
||
Attachment #8342861 -
Flags: review?(peterv)
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → bzbarsky
Status: REOPENED → ASSIGNED
Assignee | ||
Comment 4•11 years ago
|
||
Attachment #8342862 -
Flags: review?(peterv)
Assignee | ||
Comment 5•11 years ago
|
||
Also, I'd be happy to add a warning in this getter if people prefer. But addons use it a _lot_.
Updated•11 years ago
|
Attachment #8342861 -
Flags: review?(peterv) → review+
Comment 6•11 years ago
|
||
Comment on attachment 8342862 [details] [diff] [review]
part 2. Make window._content chromeonly and define it in WebIDL.
Review of attachment 8342862 [details] [diff] [review]:
-----------------------------------------------------------------
I'd really like to add the warning :-/.
Attachment #8342862 -
Flags: review?(peterv) → review+
Assignee | ||
Comment 7•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/2154019a866e
https://hg.mozilla.org/integration/mozilla-inbound/rev/537ff932d5f1
I filed bug 948096 on adding a warning.
Flags: in-testsuite-
Target Milestone: --- → mozilla29
Comment 8•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/2154019a866e
https://hg.mozilla.org/mozilla-central/rev/537ff932d5f1
Status: ASSIGNED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Comment 11•11 years ago
|
||
https://developer.mozilla.org/en-US/docs/Web/API/Window
https://developer.mozilla.org/en-US/Firefox/Releases/29/Site_Compatibility
Keywords: dev-doc-needed → dev-doc-complete
Updated•11 years ago
|
Whiteboard: [qa-]
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
•