Emilio Cobos Álvarez (:emilio) Reporter
	Description • 7 years ago

+++ This bug was initially created as a clone of Bug #1035091 +++

Bug 1035091 landed the code on early Beta and Nightly. We should switch the pref in this one.

	Emilio Cobos Álvarez (:emilio) Reporter
	Comment 2 • 6 years ago
mozreview-review

Comment on attachment 8959997 [details]
Bug 1422245 Disable @-moz-document in content pages

https://reviewboard.mozilla.org/r/228778/#review234480

Hah, so... This is fine I suppose.

There's still some breakage from it (most notably Youtube comments, bug 1426068), and all of them were using `@-moz-document url-prefix()` for that, so I think we should still parse it on content pages.

Curiously I filed bug 1446470 on that 2 days ago, and that includes this patch. Let's land this for now, I'll rebase my patches on top. Maybe mention that bug on the commit message?

Thanks!

	Emilio Cobos Álvarez (:emilio) Reporter
	Comment 3 • 6 years ago

(Or we can land this after those patches, and I'll remove part 3 on that bug, your call).

	Kohei Yoshino [:kohei]
	Comment 5 • 6 years ago

Posted the site compatibility note: https://www.fxsitecompat.com/en-CA/docs/2018/moz-document-has-been-dropped/

	Emilio Cobos Álvarez (:emilio) Reporter
	Comment 6 • 6 years ago

(In reply to Kohei Yoshino [:kohei] from comment #5)
> Posted the site compatibility note:
> https://www.fxsitecompat.com/en-CA/docs/2018/moz-document-has-been-dropped/

Beware of bug 1446470, which will fix all the known breakages so far too, and is intended to land in time for the same firefox release.

That bug means that @-moz-document url-prefix() { } will keep working.

	Kohei Yoshino [:kohei]
	Comment 7 • 6 years ago

So no security issues will be solved here? This bug can be simply WONTFIXed then... :(

	Emilio Cobos Álvarez (:emilio) Reporter
	Comment 8 • 6 years ago

Wait, what? Yes. The security issue is with other url matching functions, like regex(..), which this patch forbids. We'll just allow an empty url-prefix to avoid breaking websites.

	Kohei Yoshino [:kohei]
	Comment 9 • 6 years ago

Thanks for the clarification. Updating the note accordingly.

	Pulsebot
	Comment 10 • 6 years ago

Pushed by rgurzau@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a83ccbf8a6b6
Disable @-moz-document in content pages r=emilio

	Xidorn Quan [:xidorn] UTC+11
	Comment 11 • 6 years ago

(In reply to Emilio Cobos Álvarez [:emilio] from comment #6)
> (In reply to Kohei Yoshino [:kohei] from comment #5)
> > Posted the site compatibility note:
> > https://www.fxsitecompat.com/en-CA/docs/2018/moz-document-has-been-dropped/
> 
> Beware of bug 1446470, which will fix all the known breakages so far too,
> and is intended to land in time for the same firefox release.
> 
> That bug means that @-moz-document url-prefix() { } will keep working.

We should probably post an update to the Intent to unship thread in dev-platform about this plan as well.

	Arthur Iakab [arthur_iakab]
	Comment 12 • 6 years ago
bugherder

https://hg.mozilla.org/mozilla-central/rev/a83ccbf8a6b6

	Will Bamberg [:wbamberg]
	Comment 13 • 6 years ago

I've updated the compat data to capture this: https://developer.mozilla.org/en-US/docs/Web/CSS/@document#Browser_compatibility

Marking dev-doc-complete, but please comment if we need anything else.

	Chris Mills [:cmills]
	Comment 14 • 6 years ago

(In reply to Will Bamberg [:wbamberg] from comment #13)
> I've updated the compat data to capture this:
> https://developer.mozilla.org/en-US/docs/Web/CSS/
> @document#Browser_compatibility
> 
> Marking dev-doc-complete, but please comment if we need anything else.

I also added a rel note:

https://developer.mozilla.org/en-US/Firefox/Releases/61#CSS