W3C home > Mailing lists > Public > public-canvas-api@w3.org > July to September 2011

Re: correct and incorrect uses of canvas

From: Henri Sivonen <hsivonen@iki.fi>
Date: Fri, 15 Jul 2011 17:11:16 +0200
To: Jonas Sicking <jonas@sicking.cc>
Cc: Steve Faulkner <faulkner.steve@gmail.com>, HTMLWG WG <public-html@w3.org>, Frank Olivier <Frank.Olivier@microsoft.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, Cynthia Shelly <cyns@microsoft.com>, David Singer <singer@apple.com>, "Tab Atkins Jr." <jackalmage@gmail.com>, Edward O'Connor <hober0@gmail.com>, Canvas <public-canvas-api@w3.org>
Message-ID: <1310742676.2270.102.camel@shuttle>
On Thu, 2011-07-14 at 13:40 -0700, Jonas Sicking wrote:
> We can and should improve the
> SVG DOM to attract more people, but I suspect there will always be a
> group of people that choose to use canvas anyway due to better
> performance or other reasons.

Do you have examples of people choosing <canvas> over SVG for perf
reasons? Are the perf reasons data-based or merely assumed? Are the perf
reasons the kind of quality of implementation issues that can be
considered to be transient and addressed over the next couple of years?

In theory, SVG should be able to outperform <canvas> for painting,
because the browser engine gets to control how often to repaint, what
parts to repaint and can avoid intermediate bitmaps when the path
stroking and filling can be performed nearer hardware and there are
guaranteed not to be readbacks because the browser knows there aren't
filters in use.

So in theory, if SVG has performance issues, they should be attributable
to the DOM. If a sub-DOM is used for accessibility in the <canvas> case,
then the <canvas> case has a DOM, too.

Henri Sivonen
Received on Friday, 15 July 2011 15:11:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:31:53 UTC