W3C home > Mailing lists > Public > public-html@w3.org > January 2011

Re: An inherent flaw in <canvas>?

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 31 Jan 2011 10:50:59 -0800
Message-ID: <AANLkTikKgPFzAnvMXd_6c0bFbhzGZ99fe7pkq4NRJ5PH@mail.gmail.com>
To: Justin Anthony Knapp <justinkoavf@gmail.com>
Cc: public-html@w3.org
On Sun, Jan 30, 2011 at 11:49 PM, Justin Anthony Knapp
<justinkoavf@gmail.com> wrote:
> Should we be concerned about this?
> http://petewarden.typepad.com/searchbrowser/2011/01/a-fundamental-bug-in-html5s-canvas.html

No.  It's a fundamental restriction of an immediate-mode,
one-shape-at-a-time API that this sort of thing will happen,
especially if anti-aliasing is involved.

To fix this you need the ability to do several operations at once.
SVG addresses this by being completely retained, so the UA can figure
out when it should merge boundaries automatically.  <canvas> will gain
some sort of retained API in the future that will allow the same

In other words, this is either already fixed or will fix itself in the
future.  Nothing to be concerned about right now.

Received on Monday, 31 January 2011 18:51:52 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:08 UTC