59 bytes, text/x-review-board-request
In bug 1322517 we will remove support for EME in insecure contexts. We should add a warning when EME is used in insecure contexts, so authors have time to transition. We have 1 day of data on the telemetry probe I added to determine what proportion of contexts where EME is used are insecure, and it's showing 15% of contexts are insecure. https://mzl.la/2oWGeWs
Comment on attachment 8863306 [details] Bug 1361000 - Log a deprecation warning to the web console upon use of EME in an insecure context. https://reviewboard.mozilla.org/r/135100/#review138128 Does the console show which url (of the page, that is) is involved? If not, please include it in the warning.
Attachment #8863306 - Flags: review?(bzbarsky) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/c733f9dbec85 Log a deprecation warning to the web console upon use of EME in an insecure context. r=bz
Backed out in https://hg.mozilla.org/integration/autoland/rev/a812a96caba2 - built nicely on Windows, but everything else failed like https://treeherder.mozilla.org/logviewer.html#?job_id=95817339&repo=autoland, "Navigator.cpp:2032:31: error: ignoring return value of 'nsresult nsIDocument::GetDocumentURI(nsString&) const', declared with attribute warn_unused_result [-Werror=unused-result]"
2 years ago
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/1242d70ee6a2 Log a deprecation warning to the web console upon use of EME in an insecure context. r=bz
Posted the site compatibility note: https://www.fxsitecompat.com/en-CA/docs/2017/support-for-eme-on-insecure-contexts-has-been-deprecated/
You need to log in before you can comment on or make changes to this bug.