Are there any reasons at all not to make this a feature that simply needs/asks
a permission?
Perhaps with a short additional text "Allowing might compromise privacy". Not
only for ambient light and proximity sensors, but especially if you want to
remove device orientation information too. We a
Originally posted this on the Firefox support forum
(https://support.mozilla.org/en-US/questions/1222676), and was advised to post
this here as well.
At our Russell Group UK university, we rely on the ambient light sensor heavily
for research projects on visual perception, smart devices, etc, u
As an update here the code has landed in 60 from
https://bugzilla.mozilla.org/show_bug.cgi?id=1359076
This adds:
- Deprecation warnings for DeviceOrientation and DeviceMotion sensors.
- Deprecation errors for AmbientLight and Proximity sensors.
- Preferences to control all 4 sensors independently:
On Mon, Dec 18, 2017 at 7:36 PM, Gervase Markham wrote:
> appear.in, which supports both audio and video calling via WebRTC, works
> in Firefox for Android, although performance is not awesome on my Z3C
> Compact.
>
> It does not blank the screen when you place the device to your ear.
There might
On 12/18/17 11:36 AM, Gervase Markham wrote:
> On 18/12/17 18:25, Tantek Çelik wrote:
>> Do you know of a specific (URL?) mobile-device-capable (which
>> device(s)?) WebRTC-based audio-calling webapp that works today? I
>> would be very interested in testing it out.
>
> appear.in, which supports b
On 18/12/17 18:25, Tantek Çelik wrote:
> Do you know of a specific (URL?) mobile-device-capable (which
> device(s)?) WebRTC-based audio-calling webapp that works today? I
> would be very interested in testing it out.
appear.in, which supports both audio and video calling via WebRTC, works
in Firef
On Mon, Dec 18, 2017 at 5:52 AM, Gervase Markham 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.
I t
> 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 impleme
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,
9 matches
Mail list logo
