59 bytes, text/x-review-board-request
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.
Should cleaning up after bug 1429732 be included in this bug, or in that bug, or a new bug?
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.
Summary: Remove registerContentHandler() code in stable → Disable registerContentHandler() in stable
Comment on attachment 8974603 [details] Bug 1460481 - Disable registerContentHandler from stable releases. https://reviewboard.mozilla.org/r/242966/#review249296
Attachment #8974603 - Flags: review?(dao+bmo) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/bb0bb62a43e9 Disable registerContentHandler from stable releases. r=dao
Posted the site compatibility note: https://www.fxsitecompat.com/en-CA/docs/2018/navigator-registercontenthandler-has-been-removed/
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.
You need to log in before you can comment on or make changes to this bug.