This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues.

We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate.

For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit

For any questions, please contact owencm, sshruthi, larforge

IMPORTANT:
- This launch issue is used for standards and implementation tracking only.
It is NOT for Chrome approval regarding privacy, security, legal, UI,
testing,
accessibility etc.
- An overview of the different launch issues can be found here:
http://bit.ly/2ncKZfp
- If your feature requires security / privacy / etc approval then seek a PM
to guide you through the go/newchromefeature process

See http://www.chromium.org/blink#launch-process for an overview of the
Blink launch process, but note this doesn't cover security / privacy / etc
reviews as discussed above.

----------

Change description:
Remove access to the Speech Recognition API on insecure origins. This will prevent sites from requesting access to speech recognition over HTTP.
In practice, sites using the Speech Recognition API must already be on secure origins because the API requires access to the microphone, which is allowed only on secure origins.

Changes to API surface:
Remove support for insecure usage of Notifications

Links:
Public standards discussion: <link here>

Support in other browsers: No support
Internet Explorer:
Firefox:
Saf

Deleted: ._Apple_Pay_Payment_Mark.eps 174 bytes

._Apple_Pay_Payment_Mark.eps 174 bytes Download

Deleted: Download.zip 7.4 MB

Download.zip 7.4 MB Download