Intent to implement: report-to header as part of Reporting API

Summary: Reporting API offers 2 ways to obtain reports: ReportingObserver and Report-to Header. I implemented ReportingObserver months ago and I sent a separate intent-to-implement email about it. This email is about "report-to" header, which allows a server to specify a set of endpoints to retriev

Re: Intent to implement: report-to header as part of Reporting API

On Thu, 10 Jan 2019 at 12:27, Andrea Marchesini wrote: > web-platform-tests: just a little support. I wrote several mochitests which > can be converted to WPTs with a bit of effort. > There don't appear to be any WPT if I am looking in the right place[1]. Since Google are experimenting it feels

Re: Intent to implement: report-to header as part of Reporting API

We have some WPTs here: https://searchfox.org/mozilla-central/source/testing/web-platform/tests/content-security-policy/reporting-api/ My tests are here: - gtests: https://searchfox.org/mozilla-central/source/dom/reporting/tests/gtest - mochitests: https://searchfox.org/mozilla-central/source/dom/r

Re: Coming in Firefox 65: Dedicated Profiles Per Install and Profile Downgrade Protection

As promised here is that update. We have cleaned up the experience so that it only impacts nightly until it rides the trains and added a snazzy new first-run UI that explains what is going on. The plan is to land this at the start of the 67 nightly cycle. On Wed, Oct 31, 2018 at 10:32 AM Dave Town

XPCOM Tidying Proposal

In an effort to bring Marie Kondo memes to dev-platform, I'd like to propose an XPCOM tidying project. Through DeCOMtamination, Quantum, Fission, and other projects, we've managed to un-hide quite a few headers to C++ classes that would've otherwise been only accessible through XPCOM interfaces, m

PSA: Building Firefox for arm64 windows got a lot easier

Hi, Usual disclaimer: the following assumes this all sticks. I just landed bug 1515528 to autoland, which simplifies drastically how to build Firefox for arm64 windows, from a x86/x86_64 windows machine. At the moment, this requires some extra manual steps over mach bootstrap, because this doesn

Re: PSA: Building Firefox for arm64 windows got a lot easier

On Fri, Jan 11, 2019 at 09:24:25AM +0900, Mike Hommey wrote: > Hi, > > Usual disclaimer: the following assumes this all sticks. > > I just landed bug 1515528 to autoland, which simplifies drastically how > to build Firefox for arm64 windows, from a x86/x86_64 windows machine. > > At the moment,

Proposal to adjust our clang-format rules to include spaces after the hash for nested preprocessor directives

Hi everyone, I'd like to propose the first modification to our clang-format rules based on the feedback I've received since the switch to our new coding style from the SpiderMonkey team. The problem we're trying to solve is that in code that has nested preprocessor directives, when the directives

Re: Intent to implement: report-to header as part of Reporting API

On Thu, Jan 10, 2019 at 7:27 AM Andrea Marchesini wrote: > Summary: Reporting API offers 2 ways to obtain reports: ReportingObserver > and Report-to Header. I implemented ReportingObserver months ago and I sent > a separate intent-to-implement email about it. This email is about > "report-to" hea

Re: Proposal to adjust our clang-format rules to include spaces after the hash for nested preprocessor directives

On Thu, Jan 10, 2019 at 08:01:52PM -0500, Ehsan Akhgari wrote: The common way to deal with this problem is to indent nested preprocessor directives, very much similarly to how we indent normal code, for example: #if foo # if bar #define x 1 # else #define x 2 # endif #endif +1 This

PSA: Scroll anchoring in nightly

Hi all, Scroll anchoring (bug 1305957) is on inbound and should make it into nightly soon. If you're not familiar, take a look at the intent-to-implement post [1]. This change has the potential for web compatibility issues. If you notice a strange change in scrolling behavior, please file a bug b