Skip to content

DeviceOrientation and DeviceMotion events on insecure origins #2559

@jrstanley

Description

@jrstanley

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?

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions