Re: Intent to put Permission API's .revoke() method behind a pref

2016-08-16 Thread Martin Thomson
Sounds like a good plan. (For those who might be wondering: .request() was never exposed.) On Wed, Aug 17, 2016 at 2:48 PM, wrote: > Summary: It seems we prematurely shipped the .revoke() method on the > Permissions API before it was stable or deciding if we even wanted it in the > platform.

Intent to put Permission API's .revoke() method behind a pref

2016-08-16 Thread marcos
Summary: It seems we prematurely shipped the .revoke() method on the Permissions API before it was stable or deciding if we even wanted it in the platform. For those that don't know it: navigator.permission.revoke() allows a site to self-revoke a permission after a user has granted that permis

Re: Non-standard stuff in the /dom/ directory

2016-08-16 Thread Fabrice Desré
On 08/16/2016 09:05 PM, Kyle Huey wrote: On Tue, Aug 16, 2016 at 8:56 PM, wrote: I'm wondering, would it be worth while cleaning up the dom/ directory to move non-standard stuff out of there? There is a bunch of legacy stuff from B2G that could be moved out to, say, b2g/apis or some such fo

Re: Non-standard stuff in the /dom/ directory

2016-08-16 Thread Kyle Huey
On Tue, Aug 16, 2016 at 8:56 PM, wrote: > I'm wondering, would it be worth while cleaning up the dom/ directory to move > non-standard stuff out of there? > > There is a bunch of legacy stuff from B2G that could be moved out to, say, > b2g/apis or some such for historical reasons. > > It would

Non-standard stuff in the /dom/ directory

2016-08-16 Thread marcos
I'm wondering, would it be worth while cleaning up the dom/ directory to move non-standard stuff out of there? There is a bunch of legacy stuff from B2G that could be moved out to, say, b2g/apis or some such for historical reasons. It would make searching/working-with for standardized DOM rela

Re: Visualizing Crash Data in Bugzilla

2016-08-16 Thread Bob Clary
This is *way* cool! The historical feedback for the signatures is very compelling. I recommend everyone try it out and that we all make sure to populate the crash signature. /bc On 08/16/2016 02:47 PM, Anthony Hughes wrote: Hi Platform team, In case you don't follow planet.mozilla.org I want

Visualizing Crash Data in Bugzilla

2016-08-16 Thread Anthony Hughes
Hi Platform team, In case you don't follow planet.mozilla.org I wanted to highlight that I'm releasing the initial version of my experimental Bugzilla Tweaks add-on, dubbed Bugzilla Socorro Lens v0.3. https://ashughes.com/?p=360 In a nutshell, this inserts a graph of aggregate crash data for sig

Re: snake_case C++ in m-c (was: Re: C++ Core Guidelines)

2016-08-16 Thread Henri Sivonen
On Tue, Aug 16, 2016 at 2:19 PM, Henri Sivonen wrote: >> For GSL polyfills, I think that we should continue to follow the MFBT >> conventions set thus far and use Gecko style for naming. > > OK. I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1295611 to request mozilla::Span in MFBT. -- He

[Firefox Desktop] Issues found: August 8th to August 12th

2016-08-16 Thread Cornel Ionce
Hi everyone, Here's the list of new issues found and filed by the Desktop Release QA Team last week, *August 8 - August 12* (week 32). 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

Re: snake_case C++ in m-c (was: Re: C++ Core Guidelines)

2016-08-16 Thread Henri Sivonen
On Mon, Aug 15, 2016 at 10:30 PM, Nathan Froyd wrote: > On Mon, Aug 15, 2016 at 9:56 AM, Henri Sivonen wrote: >> Relatedly, on the topic of MFBT Range and GSL, under the subject "C++ >> Core Guidelines" Jim Blandy wrote: >>> One of the main roles of MFBT is to provide polyfills for features >>>