I'm 100% in support of this.
One thing I'd like to know though is how we're going to deal with
upstreaming patches to Skia on behalf of third parties? In my
experience, it's rarely been a case of simply submitting a patch and
having it accepted; there's normally a decent amount of engineering
I'm looking to remove the option to build mozilla-central without Skia.
Currently we default to Skia being disabled, and enable it using
--enable-skia. This is problematic because all of our officially
supported build configurations enable Skia, and as such the
Skia-is-disabled build has been
On 05/09/2016 04:59 PM, Tobias B. Besemer wrote:
But I'm pretty sure that it wouldn't take anymore long till Mozilla is on the
ground...
It seems a bit odd that you're using the "you will lose marketshare"
argument in favour of your demands, but in the content process bug your
demands
On 05/05/15 16:40, Mike Hommey wrote:
Last time I tried e10s, which was a while ago, tab switching did feel
weird with e10s *because* of that lack of the browser lock-up, because
now, the tab strip shows you've switched tabs, but the content is still
from before switching, until the spinner
On 2015-04-07 8:48 AM, Benjamin Smedberg wrote:
Is the duration of this delay measured in telemetry anywhere, and do
we have criteria for how much delay is acceptable in this case? If
e10s were off, do we expect that this same delay would occur but would
just show up as a jank switching tabs?
On 03/27/2013 07:37 PM, Robert O'Callahan wrote:
I predict that eventually we'll want to switch mozilla-central to git. (I'm
not in favour of it, but hg is not the DVCS of the future.) So, git users
not liking git's subrepositories gives me pause and I think it's imperative
to consider the
6 matches
Mail list logo
