You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: