RE: Running mochitest on packaged builds with the sandbox

Hi all, The VR team is working on a Steam packaged browser with a VR specific UI and richer VR experience. In order to prevent the overhead of having the VR specific assets included in every Firefox build while still running on tested executables, we will be doing a repack build. WebVR will

Running mochitest on packaged builds with the sandbox

Hi dev-platform, Top-line question: Do you rely on being able to run mochitests from a packaged build (`--appname`)? Context: The sandboxing team has been hard at work making the content process sandbox as restrictive as possible. Our latest focus is removing file read permissions from content

Re: Mixing nsresult and Result code

I also don't like the NS_TRY name, it seems too close to MOZ_TRY. I would prefer to avoid names which are identical except s/NS/MOZ/. Perhaps NSRESULT_TRY would be a better name? It makes it clear that it is performing the try against the nsresult type. On Mon, May 8, 2017 at 10:17 AM, Ehsan

Re: Notification() deprecation question

On Mon, May 8, 2017 at 4:24 PM, Ehsan Akhgari wrote: > AFAIK this was discussed at the spec level in > https://github.com/whatwg/notifications/issues/26 and the conclusion was to > *not* deprecate the construcutor for the non-persistent notifications. > Perhaps something

Re: Notification() deprecation question

AFAIK this was discussed at the spec level in https://github.com/whatwg/notifications/issues/26 and the conclusion was to *not* deprecate the construcutor for the non-persistent notifications. Perhaps something has changed afterwards? On 05/08/2017 03:09 AM, Chris Mills wrote: Hi there, I

Re: Mixing nsresult and Result code

I think these seem like valuable additions to nscore.h. It would be helpful to extend these facilities that would allow more code to use the Result-based programming model. (I'm not too much of a fan of the NS_TRY name, but can't think of a better name myself... :/ ) On 05/07/2017 03:34

Re: Re: CodeCoverage Monthly Update

No, currently not, but we can build one ourselves using their API (which we might to do with codecov.io anyway, since we expect to have custom needs). - Marco. Il 04/05/17 08:22, Chris Peterson ha scritto: On 2017-05-03 8:44 PM, Kyle Lahnakoski wrote: * Daily coverage reports on

[Firefox Desktop] Issues found: May 1st to May 5th

Hi everyone, Here's the list of new issues found and filed by the Desktop Release QA Team last week, *May 1 - May 5* (week 18). Additional details on the team's priorities last week, as well as the plans for the current week are available at:

Notification() deprecation question

Hi there, I found this thread recently: https://bugs.chromium.org/p/chromium/issues/detail?id=481856 Are we following the same path to deprecating Notification() and insisting people use ServiceWorkerRegistration.showNotification() instead in Gecko, or is this just a Google thing for now?