Re: Intent to Implement and Ship: Make MOZ_QUIET the default, require opt-in for DOMWINDOW/DOCSHELL logs

This sounds great. Is there a reason we can't just use MOZ_LOG for the docshell/domwindow logging? -e On Fri, Nov 8, 2019 at 2:44 PM Tom Ritter wrote: > In https://bugzilla.mozilla.org/show_bug.cgi?id=1592297 I plan/hope to > remove MOZ_QUIET and turn off the DOCSHELL/DOMWINDOW logging by defa

Announcing MozillaBuild 3.3 Release

MozillaBuild 3.3 is a minor update to version 3.2 mostly focusing on updating a few of the bundled components to newer versions. https://ftp.mozilla.org/pub/mozilla/libraries/win32/MozillaBuildSetup-Latest.exe Important changes since version 3.2: * If Git is installed it will now be available to

Re: Intent to Ship: Require user interaction for notification permission prompts

You could, but we're making this change because our user studies show users respond negatively to unexpected and unwanted prompts. If the users don't associate their triggering interaction with a desire to accomplish the task for which you're requesting permission they're still going to say "No" an

Re: Experimenting with JavaScript type safety in mozilla-central

+gtatum Also sprach Dave Townsend: > A first experiment towards understanding this has just landed ( > https://hg.mozilla.org/integration/autoland/rev/1dd081553a3a). Specifically > Greg Tatum has added TypeScript type > annotations and configuration to the JavaSc

Re: Intent to prototype: re-enabling SharedArrayBuffer

On Thu, Aug 29, 2019 at 1:47 PM Anne van Kesteren wrote: > We might ship 1 and 2 on Nightly to see what kind of breakage that > gives. A risky part of this plan is that folks will have to test for > postMessage() rather than SAB support going forward. Enabling the prototype on Nightly can be trac

Re: Experimenting with JavaScript type safety in mozilla-central

> > I know from the folks talking about types earlier, we're definitely > interested in other teams adopting some TypeScript comments in their own > areas of the codebase, so we can gather more feedback. If anyone is > interested in experimenting, I'd be happy to help guide some initial setup. > I

Re: Experimenting with JavaScript type safety in mozilla-central

I was getting ready to write up some updates, but was waiting for some of my most recent type work to land. I'll go ahead since there is interest. So far the experience of working in devtools/client/performance-new [0] has been really positive. It's a bit challenging getting the TypeScript module s

[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/y2atdpjj. Bugs logged by Desktop Release QA in the last

Re: Intent to unship: DTLS 1.0 for WebRTC

This is somewhat more aggressive than our plans for HTTPS. The usage rate is significantly higher (that's about 3x) and we don't have DTLS 1.3 yet, though the spec is now close to publication. On balance, this is still justifiable given the nature of this feature. On Fri, Nov 8, 2019 at 5:29 PM

Re: Intent to Implement- Double-keyed HTTP cache

On Wed, Aug 21, 2019 at 7:40 PM Sebastian Streich wrote: > Estimated or target release: Firefox 70 The plan is to enable this on Firefox 72 Nightly to see if there's any fallout that needs addressing. It will not ride the trains. This is tracked by https://bugzilla.mozilla.org/show_bug.cgi?id

Re: Intent to prototype: heading levels

Unfortunately, this was not a success (too many h1s got adjusted to be h2s) so we've removed this code and abandoned this particular plan for dealing with heading levels in HTML: https://bugzilla.mozilla.org/show_bug.cgi?id=1590366. ___ dev-platform maili