New Policy: Marking Bugzilla bugs for features riding behind a pref

Hello, We control enabling many features and changes to Firefox using preferences. Program and Release management as well as PI need a better view of this. We've written a new policy which you can read on our nascent bug-handling mini-site:

Proposed W3C Charter: WebRTC Working Group

The W3C is proposing a revised charter for: WebRTC Working Group https://www.w3.org/2018/04/webrtc-charter.html https://lists.w3.org/Archives/Public/public-new-work/2018Apr/0008.html Mozilla has the opportunity to send comments or objections through Friday, May 25. The changes relative to

Proposed W3C Charter: Devices and Sensors Working Group

The W3C is proposing a revised charter for: Devices and Sensors Working Group https://w3c.github.io/dap-charter/DeviceAPICharter.html https://lists.w3.org/Archives/Public/public-new-work/2018Apr/0010.html Mozilla has the opportunity to send comments or objections through Friday, May 25.

Proposed W3C Charter: Distributed Tracing Working Group

The W3C is proposing a charter for a new working group: Distributed Tracing Working Group https://www.w3.org/2018/04/distributed-tracing-wg-charter.html https://lists.w3.org/Archives/Public/public-new-work/2018Apr/0005.html Mozilla has the opportunity to send comments or objections through

Proposed W3C Charter: Timed Text Working Group

The W3C is proposing a revised charter for: Timed Text Working Group https://www.w3.org/2018/04/proposed-tt-charter-2018.html https://lists.w3.org/Archives/Public/public-new-work/2018Apr/0003.html Mozilla has the opportunity to send comments or objections through Thursday, May 17. The

Re: Firefox 60 Beta build error on ARM

This sounds like https://bugzilla.mozilla.org/show_bug.cgi?id=1434589 which currently doesn't have a fix. You might be able to work around it for now with --disable-webrtc. On Wed, May 2, 2018 at 1:08 PM, Charles G Robertson wrote: > Hi, > > I'm trying to build Firefox 60

Firefox 60 Beta build error on ARM

Hi, I'm trying to build Firefox 60 Beta on Arm64 and seeing this error: ... g++: error: unrecognized command line option '-msse2' gmake[4]: *** [/home/abuild/rpmbuild/BUILD/mozilla/config/rules.mk:1049: Unified_cpp_common_audio_sse2_gn0.o] Error 1 gmake[3]: ***

Re: Intent to implement: AudioWorklet

It's great to see the intent for the AudioWorklet, but also I can see the GC observability is still being discussed here. Karl, can you open a new spec issue if you think this needs another look from AudioWG and TAG? -Hongchan On Wednesday, May 2, 2018 at 8:17:30 AM UTC-7, Boris Zbarsky

Re: Intent to implement: AudioWorklet

On 5/2/18 5:21 AM, Karl Tomlinson wrote: [[AudioNode Lifetime]] https://github.com/WebAudio/web-audio-api/issues/1471 I've read through that thread, but I'm still a little unclear on where thing stand. With the latest proposal, can there be observable situations where the output sound

Maintenance work on perf-html.io, planned for May 3 at 8am PDT, small downtime planned

Hi, Tomorrow we'll move perf-html.io to a new home. As part of this switch we'll chance the DNS servers so that they point to the new hosting at netlify.com. This should be painless. However as part of the process we also need to generate new TLS certificates, and we can do this only once

Re: Intent to implement: AudioWorklet

On Wed, May 2, 2018, at 11:34 PM, Tom Ritter wrote: > On Wed, May 2, 2018 at 5:11 AM, Robert O'Callahan > wrote: > > On Wed, May 2, 2018 at 9:21 PM, Karl Tomlinson wrote: > > > >> It seems that Chrome works around this by choosing to garbage > >> collect

Re: Default Rust optimization level decreased from 2 to 1

Le 25/04/2018 à 18:26, Bobby Holley a écrit : Could we instead have the profiler UI throw up a warning if the build was not compiled with --enable-release? I filed https://github.com/devtools-html/perf.html/issues/976 to discuss about it. Thanks, -- Julien

Re: Intent to implement: AudioWorklet

On Wed, May 2, 2018 at 5:11 AM, Robert O'Callahan wrote: > On Wed, May 2, 2018 at 9:21 PM, Karl Tomlinson wrote: > >> It seems that Chrome works around this by choosing to garbage >> collect input nodes even when their presence is specified to >> require

Re: QA Firefox 62 feature testing pi-requests deadline is May 2

Hi, Just a reminder that today is the deadline for submitting PI requests for Fx 62. Regards, Tom On Tue, Apr 24, 2018 at 9:16 PM, Tom Grabowski wrote: > Hi, > > Similar to what QA did for previous Firefox feature testing prioritization >

Re: Intent to implement: AudioWorklet

On Wed, May 2, 2018 at 9:21 PM, Karl Tomlinson wrote: > It seems that Chrome works around this by choosing to garbage > collect input nodes even when their presence is specified to > require (observable) AudioWorkletProcessor.process() calls. > This garbage collection is

Intent to implement: AudioWorklet

=Summary/benefits: "The AudioWorklet object allows developers to supply scripts (such as JavaScript or WebAssembly code) to process audio on the rendering thread, supporting custom AudioNodes." [[Concepts]] Allowing scripts to process audio on the rendering thread is important for low latency