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

Re: Separate Draft of Canvas API Uploaded to CVS

From: Doug Schepers <schepers@w3.org>
Date: Tue, 18 Aug 2009 15:40:14 -0400
Message-ID: <4A8B039E.6060907@w3.org>
To: public-canvas-api@w3.org
Hi, Jun-

FUJISAWA Jun wrote (on 8/18/09 5:17 AM):
>>  I took the opportunity to make it a little more generic (i.e., not
>>  HTML-specific), so that SVG could also include the Canvas API (for
>>  example, to be used on<image>  elements in SVG);
> As for the use of in SVG, I think the Canvas API would be useful for any
> elements that establish a new viewport, including 'svg', 'image', 'video',
> 'animation', and 'foreignObject' elements.
> There is no element that provide graphics rendering context in HTML, so
> we need to introduce 'canvas' element. In the case of SVG, however, we
> already have a good set of graphics elements with independent rendering
> contexts, and we should take full advantage of the available rich
> features of SVG.

To be honest, I hadn't considered anything but <image>, but we can 
certainly take a look at other elements.  I definitely see some 
interesting use cases for using it with <video>, in fact.

-Doug Schepers
W3C Team Contact, SVG and WebApps WGs
Received on Tuesday, 18 August 2009 19:40:25 UTC

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