Intent to Prototype: CSS Masonry layout

Summary: Masonry layout is a popular idea of how to lay out content on the web, e.g. a Pinterest wall of images. I've made a detailed proposal on how to support this natively as feature of CSS Grid here: https://github.com/w3c/csswg-drafts/issues/4650 The feedback has been overwhelmingly positive

Upcoming C++ standards meeting in Prague

Hi everyone! The next meeting of the C++ Standards Committee (WG21) will be February 10-15 in Prague, Czech Republic. This meeting will continue to focus on bug fixing and stabilization for C++20, which has achieved feature-complete status in July 2019, and whose Draft International Standard

Removing support for non-nsISupports XPIDL interfaces

In times of old, you could declare an XPIDL interface that didn't inherit from nsISupports, as long as it only had constants in it. I'm not sure why it was really such a burden to make it inherit from nsISupports. Anyways, it appears that our de-COM efforts have proceeded far enough that this

[desktop] Bugs logged by Desktop Release QA in the last 7 days

Hello, Here's the list of new issues found and filed by the Desktop Release QA team in the last 7 days. Additional details on the team's priorities last week, as well as the plans for the current week are available at: https://tinyurl.com/yfwt3p5x. Bugs logged by Desktop Release QA in the

Re: Proposed W3C Charter: WebAssembly Working Group

I've been involved in the re-drafting of this charter as part of the regular wasm WG meetings and I think we should support it. Cheers, Luke On Tue, Jan 21, 2020 at 11:10 AM L. David Baron wrote: > The W3C is proposing a revised charter for: > > WebAssembly Working Group >

Volunteers needed for nightly crash triage rotation

[cross-posting to firefox-dev and stability] Due to the recent layoffs the nightly crash triage roster has a lot of holes so if you have some spare cycles please come and help out! Nightly crash triage consists in looking at the crashes for a specific version of nightly (e.g. the previous week

Fission meetings at the Berlin All Hands

The Fission team will be hosting a few meetings at the Berlin All Hands to help Firefox frontend and Gecko engineers convert their code to Fission's async APIs. Step 1: attend the "Introduction to Fission Engineering" presentation to get an overview and code examples of Fission: * Sched:

Re: Searchfox at All-Hands: Who's interested?

Following up, there are now 2 identical Searchfox sessions scheduled hosted by some permutation of myself and Emilio and any other Searchfox experts who show up!  If you are interested, hopefully you can attend part of one of the sessions.  It's okay to show up late, the goal is to help people

Re: Intent to ship: Optional Chaining Operator

Just a note: Please be conservative about using this in m-c while it's not enabled in release yet, to avoid issues when uplifting patches. Otherwise, I think this is a great new feature that I'd love to use. On Wed, Jan 22, 2020 at 4:30 PM Patrick Brosset wrote: > Thanks Yulia, this is going to

Re: Intent to ship: Optional Chaining Operator

On Wednesday, January 22, 2020 at 4:30:33 PM UTC+1, Patrick Brosset wrote: > Thanks Yulia, this is going to be very useful and helpful in reducing code > complexity! > > For info, here's a DevTools bug to make sure the console panel still > supports autocompletion even when ?. is used: >

Re: Intent to ship: Optional Chaining Operator

ESLint doesn't implement new features until they are stage 4, so it tends to lag behind a bit. Hence at the moment, you won't be able to use these in our code. ESLint's tracking issue is here , and it looks like they've started working on it, so