W3C home > Mailing lists > Public > public-html@w3.org > July 2007

Re: Use Cases for The <canvas> Element

From: James Graham <jg307@cam.ac.uk>
Date: Sun, 29 Jul 2007 22:51:03 +0100
Message-ID: <46AD0BC7.8030507@cam.ac.uk>
To: "Patrick H. Lauke" <redux@splintered.co.uk>
Cc: public-html <public-html@w3.org>, wai-xtech@w3.org

Patrick H. Lauke wrote:
> 
> Lachlan Hunt wrote:
> 
>> That's technically true, but in this case, we already have at least 3 
>> native implementations in Firefox, Opera and Safari
> 
> Sorry to drag this on, but...if this is a valid path for discussion, 
> then, compare table headers attribute and their implementation in JAWS 
> etc. Why is THAT implementation less important than that of canvas?

It is a valid reasoning and is an advantage of the headers attribute 
over other solutions that meet that use case. However it does not follow 
that if <canvas> is accepted over scripting+<img> (the only serious 
alternative I remember being suggested for scripted production of 
bitmaps; SVG is used for an entirely different type of drawing that 
meets different needs and is substantially more complex to implement), 
headers must therefore be included ahead of any proposed alternatives; 
it also depends on the other arguments for and against the proposed 
solutions.

-- 
"Mixed up signals
Bullet train
People snuffed out in the brutal rain"
--Conner Oberst
Received on Sunday, 29 July 2007 21:51:06 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:47 UTC