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

My thanks to everyone who had commented on this so far. I’m replying to your questions and comments in this email so that we don’t have a threading catastrophe. First, several of you mentioned the typo where I wrote qa-verify when the flag is qe-verify. The policy document has the correct flag

Re: Intent to implement: AudioWorklet

Looks like the existing WebAudio issue https://github.com/WebAudio/web-audio-api/issues/1471 is where this should get resolved (for people who haven’t switched over there yet). Best regards Nils Ohlmeier > On May 2, 2018, at 09:05,

Re: Proposed W3C Charter: Devices and Sensors Working Group

Filling in some of the gaps here: WakeLock API is still used on android, afaik so we don't let the phone turn off while playing media. We ship the Vibration API on android, have since FxOS. Not much happening there these days, other than some discussion about permissions around it. We still

Intent to ship: event.srcElement

Summary: A .srcElement property on events that is an alias of .target. It's originally an IE-ism that now everyone but us supports. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=453968 Standard: https://dom.spec.whatwg.org/#dom-event-srcelement Target release: Firefox 62 Preference:

Re: Should web specifications try to describe object lifetimes? [was Intent to implement: AudioWorklet]

On 5/4/18 3:34 AM, Karl Tomlinson wrote: Not sure I understand your question, but the observable behavior described by this section, or specifically "Before an AudioNode is deleted, it will disconnect itself from any other AudioNodes" Right. So that observably influences the sound produced or

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

I have a bug that will introduce a pref/feature-flag, but that is just one bug that blocks a meta bug. The meta bug covers the whole feature. Should these flags get set on the meta bug or on the bug that introduces the pref? Testing the specific bug that introduces the pref won't provide much

Re: Should web specifications try to describe object lifetimes? [was Intent to implement: AudioWorklet]

Boris Zbarsky writes: > So if there is in fact a problem still remaining, convincing Alex > that it's there is pretty valuable. Having him convinced it > doesn't exist is actively harmful as far as getting it fixed goes. Thank you. Alex sounds like a very valuable person to get on side. We

Re: Proposed W3C Charter: Devices and Sensors Working Group

On Fri, May 4, 2018 at 2:07 AM, L. David Baron wrote: > On the flip side, sensor APIs are offered by mobile (and to some > degree desktop) operating systems and widely used by apps running on > them, and there's clear demand for having them on the Web. So I > think it seems