Boris Zbarsky [:bzbarsky] Assignee
	Description • 11 years ago

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?

	Boris Zbarsky [:bzbarsky] 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.

	Boris Zbarsky [:bzbarsky] 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.

	Boris Zbarsky [:bzbarsky] 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_.

	Peter Van der Beken [:peterv]
	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 :-/.

	Boris Zbarsky [:bzbarsky] 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.

	Ryan VanderMeulen [:RyanVM]
	Comment 8 • 11 years ago

https://hg.mozilla.org/mozilla-central/rev/2154019a866e
https://hg.mozilla.org/mozilla-central/rev/537ff932d5f1

	Boris Zbarsky [:bzbarsky] Assignee
	Comment 9 • 11 years ago

I guess this is technically site-compat.

	Kohei Yoshino [:kohei]
	Comment 11 • 10 years ago

https://developer.mozilla.org/en-US/docs/Web/API/Window
https://developer.mozilla.org/en-US/Firefox/Releases/29/Site_Compatibility