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 goals
On Sun, Aug 12, 2012 at 4:20 PM, Antonio Gomes toniki...@gmail.com 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
On Aug 10, 2012, at 3:47 PM, Alpha Lam hc...@chromium.org 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
On Sun, Aug 12, 2012 at 1:24 PM, Maciej Stachowiak m...@apple.com 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
And down it goes again...
On Fri, Aug 10, 2012 at 11:14 AM, Levi Weintraub le...@google.com wrote:
We're back!
On Fri, Aug 10, 2012 at 8:07 AM, Peter Beverloo pe...@chromium.orgwrote:
It's been down for the past hour, again. Just a nudge in case it slipped
through.
Peter
On Thu, Aug
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 pkast...@chromium.org wrote:
On Sun,
On Aug 12, 2012, at 6:26 PM, Florin Malita fmal...@google.com 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 le...@google.com wrote:
We're back!
On Fri, Aug 10, 2012 at 8:07 AM,
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%
8 matches
Mail list logo
