W3C home > Mailing lists > Public > public-fx@w3.org > January to March 2011

Re: Thoughts on canvas compositing

From: Robert O'Callahan <robert@ocallahan.org>
Date: Mon, 17 Jan 2011 10:55:02 +1300
Message-ID: <AANLkTi=43hoJmg03+=JyLtMaryeMgFUoQ_-OfCoP6WYz@mail.gmail.com>
To: Simon Fraser <smfr@me.com>
Cc: Paul Bakaus <pbakaus@zynga.com>, "public-canvas-api@w3.org" <public-canvas-api@w3.org>, "public-fx@w3.org" <public-fx@w3.org>
On Mon, Jan 17, 2011 at 10:18 AM, Simon Fraser <smfr@me.com> wrote:

> That's not true of all user agents. For example, WebKit on Mac will use a
> fast, GPU-based path for compositing a WebGL canvas. It's also able to do
> this while preserving correct CSS rendering in most cases; for example, you
> can position other HTML content on top of the WebGL.
>

The same is true for Firefox 4 everywhere we have enabled usage of the GPU
(currently Mac and Windows for drivers we trust). I believe it's also true
for IE9. It's also true for 2D canvas on those browsers.

I really don't see the need for any new properties. I think the onus is on
> the browser developers to detect and implement compositing optimizations
> when they can.
>

I agree.

Rob
-- 
"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]
Received on Sunday, 16 January 2011 21:56:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 16 January 2011 21:56:33 GMT