Re: Rationalising Linux audio backend support

On Wed, Mar 29, 2017 at 3:40 AM, Henri Sivonen wrote: > Arguably, system configuration info belongs under FHR, so it would not > be optimal if the Pulse check wasn't there but was in opt-in Telemetry > instead. Where was it? The check was marked opt-out.

Re: Intent to implement and ship: support ::cue pseudo-element from document.

On Wednesday, March 29, 2017 at 11:21:06 PM UTC+13, bec...@mozilla.com wrote: > Summary: > We are going to support ::cue(with no argument) pseudo-element for webvtt. > It allows styling the webvtt subtitle/caption text during video playback. > > Bug:

Re: windows build anti-virus exclusion list?

On Sun, Mar 26, 2017 at 11:56 PM, Jean-Yves Avenard wrote: > Hi. > > I have received the new Dell XPS 15 9560 and got very puzzled as to why > compiling central was so slow on this machine. > This is comparing against a Gigabyte Aero 14 with a gen 6 intel CPU > (2.6Ghz

Re: Async Iteration is available on non-release-only, for testing purpose

thanks for the input :) re-landed them disabling on chrome/addon, with a test that checks they're not available on chrome code. -- arai > 2017/03/28 1:38、Shu-yu Guo のメール: > > Cross-posting to firefox-dev. > > TL;DR: > > arai has done truly excellent feature work

Re: Rationalising Linux audio backend support

On Wed, Mar 29, 2017 at 12:29 PM, Kurt Roeckx wrote: > The FAQ seems to suggest that telemetry is only enabled in the pre-release > versions > and not in the release versions. I assume there is a bias that is caused by > this. There are two types of telemetry: "Firefox Health

Re: Rationalising Linux audio backend support

Den torsdag 14 juli 2016 kl. 04:31:50 UTC+2 skrev ajo...@mozilla.com: > Supporting two separate audio backends in Linux is duplicated effort. > > I took over the platform media playback team at Mozilla a little over 3 years > ago. At that point we only supported WebM/VP8/Vorbis,

Re: Rationalising Linux audio backend support

Den torsdag 14 juli 2016 kl. 09:32:51 UTC+2 skrev Jet Villegas: > I generally support reducing the support matrix for Linux PCM audio. > > A quick search for "ALSA vs. PulseAudio" comes up with mixed reviews for > either, which probably explains why we have both. It also seems like we can > count

Intent to implement and ship: support ::cue pseudo-element from document.

Summary: We are going to support ::cue(with no argument) pseudo-element for webvtt. It allows styling the webvtt subtitle/caption text during video playback. Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1318542 Spec: https://w3c.github.io/webvtt/#the-cue-pseudo-element Platform coverage:

Re: Rationalising Linux audio backend support

On 2017-03-22 19:34, Botond Ballo wrote: Now that this change has hit the release channel, we've started receiving feedback from a wider range of users, a lot of it in bug 1345661 [1]. I believe the feedback in that thread brings some new information to the table that we weren't aware of when

MOZ_DEBUG_CHILD_PAUSE is now more flexible

The environment variable MOZ_DEBUG_CHILD_PAUSE can now be set to the time in seconds that you want new content processes to sleep for just after they start (to give time to attach a debugger). For backwards compatibility, setting the value to 1 is special and maintains the old behavior of 30s

Re: Rationalising Linux audio backend support

Henri Sivonen writes: > It's a problem if distros disable FHR by default Probably a regression from bug 722240. Did Mozilla contact downstream maintainers they now have to explicitly opt-in? Bug 1233687 suggests the answer is "no", favoring one distro over the others. >

Re: Rationalising Linux audio backend support

Botond Ballo writes: > Anyways, there is no conflict between supporting ALSA and supporting > 5.1 sound. As has been mentioned earlier in the thread, ALSA has since > added support for 5.1, and so IIUC it's just our wrapper library > (libcubeb) that needs the support added.