> Is it fair to say that after removal of the Proximity Sensor API, no e.g. WebRTC-based audio-calling webapp will be able to blank the screen when the user holds the device to their ear?
Yes, however this would be the case for all other browsers too. Given that we are the only browser to implement the event based interface <https://developer.mozilla.org/en-US/docs/Web/API/Proximity_Events> for this I don't think we should block on the loss of this feature. The next generation of these APIs are going through TAG review where many of the concerns here are still being addressed: https://github.com/w3ctag/design-reviews/issues/207 <https://github.com/w3ctag/design-reviews/issues/207> We may be able to reimplement this functionality with the new APIs with far less granular access and prompted if more granular is needed. There has also been no real intent from browser makers to ship them despite their improvements. Thanks On Mon, Dec 18, 2017 at 7:52 AM, Gervase Markham <[email protected]> wrote: > On 17/12/17 15:29, Jonathan Kingston wrote: > > I am suggesting the removal of both Ambient Light and Proximity Sensor > APIs > > via a preference so we can ensure there is no adverse impact to the web > > with a quick mitigation if needed. > > Is it fair to say that after removal of the Proximity Sensor API, no > e.g. WebRTC-based audio-calling webapp will be able to blank the screen > when the user holds the device to their ear? > > That seems sad. > > Gerv > > _______________________________________________ > dev-platform mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
