W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2013

Re: [whatwg] Enabling LCD Text and antialiasing in canvas

From: Rik Cabanier <cabanier@gmail.com>
Date: Fri, 22 Feb 2013 11:01:49 +1100
Message-ID: <CAGN7qDB2M7r9AYyZavPo11NL7hRBXuNT+0SHdXe=OF8_kZK5iQ@mail.gmail.com>
To: robert@ocallahan.org
Cc: whatwg@whatwg.org, Ian Hickson <ian@hixie.ch>, Stephen White <senorblanco@chromium.org>
On Fri, Feb 22, 2013 at 10:33 AM, Robert O'Callahan <robert@ocallahan.org>wrote:

> I think Rik is convincing me that we shouldn't expose mozOpaque or any
> other explicit subpixel AA control to the Web. It will be very easy for Web
> authors to test it in one place and discover that it works without
> realizing that they're causing problems for some users.
> I think a fully automatic solution that tries to use subpixel AA but is
> always able to render grayscale AA if needed is the way to go. Possibly
> with an author hint to suggest opting into a more expensive rendering path.
Great! I think matteColor (or matteStyle to be more consistent) can easily
be implemented. We can optimize rendering later.

So, if a mattecolor is set the UA can assume that:
- all compositing operation within the canvas can ignore background alpha
- the canvas can be copied directly to the screen (unless another effect is
applied to the canvas element or its ancestor)

If mattecolor is set, the UA should matte with that color. If a compositing
operation (that introduces alpha) is used, the matte operation needs to be

Received on Friday, 22 February 2013 00:02:15 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:19 UTC