Browser manufacturers like Mozilla or Google regularly add new features to browsers. The new API, sensor API, is just an example, adding new functions that may be used by sites and applications.
API may expose data to sites and services, and may even make sites control functions. Web browsers such as Firefox or Chrome support permissions that allow users to control these functions.
Sensor permissions only apply to Chrome CanaryAndroid and desktop versions. This option is supported.
Canary is a development version of Google Chrome; This feature usually takes several months to appear in the stable version of Chrome browser.
Google has added global and per-site sensor access control in Chrome web browser, which users of web browser can use to control access to the sensor API in the browser.
By default, access to the sensor is enabled.
If you prefer, you can disable the sensor globally or by site. Here's what you should do:
Load Chrome://settings/content/sensors in the chrome address bar. Doing so will open sensor permissions in the browser.
Toggle "Allow sites to use motion and light sensors" to globally enable or disable sensors.
Sites you added to the Allow or Block list will also be displayed there.
Tip: load chrome:// settings/content/ to manage the permissions of other APIs and functions. Most (such as microphones or cameras) are set to Ask, which means that Chrome will display a prompt when it detects an attempt to access these APIs.
This option also applies to each site. Just activate the icon chrome in front of the URL and you can start using it.
Chrome may display a direct option to allow or block motion or light sensors on specific websites. You can also access the website settings by activating this link.
These show all the permissions supported by Chrome. Your changes to the site permissions are only valid for the selected site. You can use these options to override global permissions, such as allowing or blocking a feature on the website.
Chrome Canary 75 provides an option to block access to the sensor API, and Google has not revealed when this feature will be available in a stable version. The stable version of Chrome 75 may be the target, about 2-3 months.