DeviceOrientation and DeviceMotion events on insecure origins #2559

jrstanley opened this Issue Jun 7, 2016 · 0 comments


None yet
2 participants

jrstanley commented Jun 7, 2016

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?

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