Re: Disabling C++ tests by default?

On Fri, Oct 2, 2015 at 1:03 PM, Ehsan Akhgari wrote: > On 2015-10-02 2:42 PM, Jonas Sicking wrote: >> >> It might still mean that we can save time on tryserver if we only >> build these by default if the user has opted in to running the >> relevant tests. >> >> I agree

Re: Content sniffing: seeking reliable protection of a text HTTP resource

On 10/1/15 5:36 PM, Incnis Mrsi wrote: First is “media type (a.k.a. MIME) sniffing”, when browser overrides media type/subtype. This is implemented in toolkit/components/mediasniffer/nsMediaSniffer.cpp component (and possibly others, don’t know). Note that these are generally very conservative

Is APZ meant to be a permanent part of the platform?

APZ is wonderful, making the web feel smooth when a page's demands would otherwise cause jank. In many cases, it's the *only* reason we're able to create decent experiences today, particularly on mobile. It does, however, highlight a shortcoming of our platform today: we can't achieve flawless

Re: Is APZ meant to be a permanent part of the platform?

On Mon, Oct 5, 2015 at 7:20 AM, Marcus Cavanaugh wrote: > APZ is wonderful, making the web feel smooth when a page's demands would > otherwise cause jank. In many cases, it's the *only* reason we're able to > create decent experiences today, particularly on mobile. > > It does,

Re: Is APZ meant to be a permanent part of the platform?

On Sun, Oct 4, 2015 at 2:20 PM, Marcus Cavanaugh wrote: > we can't > achieve flawless 60fps performance without APZ. We can get close, but any > nontrival-but-reasonable demo will encounter jank, ostensibly due to > compositing and rendering taking too much time. (APZ pathways,