Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DeviceOrientation and DeviceMotion events on insecure origins #2559

Open
jrstanley opened this issue Jun 7, 2016 · 0 comments
Open

DeviceOrientation and DeviceMotion events on insecure origins #2559

jrstanley opened this issue Jun 7, 2016 · 0 comments

Comments

@jrstanley
Copy link
Contributor

@jrstanley jrstanley commented Jun 7, 2016

http://caniuse.com/#search=devicemotion

Chrome is showing deprecation warnings in the console when using DeviceOrientation or DeviceMotion events on insecure origins. These are currently deprecate and will be removed in the future. No timescale seems to be set.

https://sites.google.com/a/chromium.org/dev/Home/chromium-security/deprecating-powerful-features-on-insecure-origins
https://bugs.chromium.org/p/chromium/issues/detail?id=464874

A number of features are expected to be removed on insecure origins, including GeoLocation (see #2504).

Is there merit in considering a way of marking features as only being available on secure/insecure origins? There is a further issue in the interim which is marking deprecation and the availability of a feature on secure or insecure versions depending on the browser.

Alternatively, and more simply, is there merit in adding some detail to the notes section?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants