Re: [webkit-dev] Unprefixing Blob.webkitSlice() ?

2012-08-12 Thread Kinuko Yasuda
As a quick follow-up, in Chrome 21 the usage histogram tells ~80% of slice call is still using webkitSlice (no wonder as unprefixed slice was rolled out just half a month ago). Since we started showing a deprecation message I hope the number changes over time. slice usage: 22.61% webkit

Re: [webkit-dev] bugs.webkit.org and trac.webkit org down?

2012-08-12 Thread Dirk Schulze
On Aug 12, 2012, at 6:26 PM, Florin Malita wrote: > And down it goes again… It is down for me as well… Dirk PS: Sorry, I always wanted to that :D > > On Fri, Aug 10, 2012 at 11:14 AM, Levi Weintraub wrote: > We're back! > > > On Fri, Aug 10, 2012 at 8:07 AM, Peter Beverloo wrote: > It's

Re: [webkit-dev] Status of multithreaded image decoding

2012-08-12 Thread Maciej Stachowiak
I that case, starting async decoding at layout time makes sense if and only if at layout to e you can predict what you will paint. I don't know enough about our rendering to know of that is the case. - Maciej On Aug 12, 2012, at 5:34 PM, Peter Kasting wrote: > On Sun, Aug 12, 2012 at 1:24

Re: [webkit-dev] bugs.webkit.org and trac.webkit org down?

2012-08-12 Thread Florin Malita
And down it goes again... On Fri, Aug 10, 2012 at 11:14 AM, Levi Weintraub wrote: > We're back! > > > On Fri, Aug 10, 2012 at 8:07 AM, Peter Beverloo wrote: > >> It's been down for the past hour, again. Just a nudge in case it slipped >> through. >> >> Peter >> >> >> On Thu, Aug 9, 2012 at 10:4

Re: [webkit-dev] Status of multithreaded image decoding

2012-08-12 Thread Peter Kasting
On Sun, Aug 12, 2012 at 1:24 PM, Maciej Stachowiak wrote: > Why not start asynchronous decoding immediately as the image is loading, > and synchronize at paint time? What is the benefit of waiting until layout > time to start decoding the image data? > Uninformed guess (since I haven't touched t

Re: [webkit-dev] Status of multithreaded image decoding

2012-08-12 Thread Maciej Stachowiak
On Aug 10, 2012, at 3:47 PM, Alpha Lam wrote: > This is a very valid concern. The question you raised is one topic I want to > discuss more broadly. > > Chromium has a separate rasterization stage so there is some time for > decoders to work, synchronization can happen in rasterization stage.

Re: [webkit-dev] Chromium for Android builders have been added to the EWS

2012-08-12 Thread Peter Beverloo
On Sun, Aug 12, 2012 at 4:20 PM, Antonio Gomes wrote: > Nice work. I assume your upstreaming is done. > We are getting very close! API compatibility is the next milestone (which only is one or two APIs away at this point), after which the remaining code is mostly long-term work (Text Autosizing

Re: [webkit-dev] Chromium for Android builders have been added to the EWS

2012-08-12 Thread Antonio Gomes
Nice work. I assume your upstreaming is done. On Fri, Aug 10, 2012 at 6:47 AM, Kenneth Rohde Christiansen < kenneth.christian...@gmail.com> wrote: > Nice to hear and congratulation with getting so far! > > I am very happy that you are aiming at having a working mobile port in > trunk; similar goa