Jonathan Kingston [:jkt] he/him Assignee
	Description • 6 years ago

As outlined in the intent to unship (https://groups.google.com/forum/#!topic/mozilla.dev.platform/jeTDLz38_RE/discussion) we should remove the code from stable. This bug is to disable the code in stable for now.

	Andrew Cook
	Comment 2 • 6 years ago

Should cleaning up after bug 1429732 be included in this bug, or in that bug, or a new bug?

	Jonathan Kingston [:jkt] he/him Assignee
	Comment 3 • 6 years ago

I'll make a new bug for that, in my super tired state I made this patch message have the wrong function name. We should remove the actual code after 62 is stable imo just to ensure we don't break anything.

	Jonathan Kingston [:jkt] he/him Assignee
	Comment 5 • 6 years ago

Clean try push: https://treeherder.mozilla.org/#/jobs?repo=try&revision=3e325c035d2398216c253e44a5673dea00bea1d6

	Dão Gottwald [:dao]
	Comment 6 • 6 years ago
mozreview-review

Comment on attachment 8974603 [details]
Bug 1460481 - Disable registerContentHandler from stable releases.

https://reviewboard.mozilla.org/r/242966/#review249296

	Pulsebot
	Comment 7 • 6 years ago

Pushed by jkingston@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/bb0bb62a43e9
Disable registerContentHandler from stable releases. r=dao

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

Posted the site compatibility note: https://www.fxsitecompat.com/en-CA/docs/2018/navigator-registercontenthandler-has-been-removed/

	Eliza Balazs [:ebalazs_]
	Comment 9 • 6 years ago
bugherder

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

	Eric Shepherd [:sheppy]
	Comment 10 • 6 years ago

The article has been updated slightly, and I’ve submitted PR #2440 to update the BCD database to indicate this change.

This is also listed on Firefox 62 for developers.