Hi Myk,
Thanks for the response.
did you find any reference for legal requirements where it say that we can ship
xulrunner application with its own copy of firefox.
I hope you have notice this too because if we launch the application with .bat
script using firefox then under the task manager t
On Thu, Nov 30, 2017 at 2:15 AM, Ting-Yu Lin wrote:
> Thank you for all the feedback. I feel the safest plan is to ship the entire
> module at once. It also saves some work to implement two preferences to
> exclude the shape-outside: value which we don't render in the first
> stage.
Thanks for g
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
DOMPreferences was introduced (but it's not landed yet because of some
mochitest failures) to cleanup how preferences are managed by workers.
Preferences getters/setters are main-thread only and, currently, in order
to propagate a white-list of prefs [1], we have to dispatch runnables to
any activ
> 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,
On 18/12/2017 03:38, Nicholas Nethercote wrote:
I am working on a redesign that will fix a lot of the problems. There was a
meeting about this in Austin. I hope to implement this in Q1 2018.
Yay!
If you have changes related to Prefs, please let me (or another Prefs peer)
know about it. Thanks
Hi everyone,
Here's the list of new issues found and filed by the Desktop Release QA Team
last week, December 11 - December 15 (week 50).
Additional details on the team's priorities last week, as well as the plans for
the current week are available at:
https://public.etherpad-mozilla.org/p/De
11 matches
Mail list logo
