W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2007

[whatwg] Why Canvas?

From: Anne van Kesteren <annevk@opera.com>
Date: Wed, 01 Aug 2007 09:50:47 +0200
Message-ID: <op.twdeqxr464w2qv@annevk-t60.oslo.opera.com>
On Wed, 01 Aug 2007 01:34:01 +0200, WeBMartians <webmartians at verizon.net>  
wrote:
> Why not allow the graphics primitives to operate on any element (not  
> just <canvas>) that has a height and width that may be expressed in  
> picture elements... ...even window.screen with its .availHeight,  
> .availWidth, .height, and .width (yeah, I know, the Screen object is  
> actually a JavaScript object, not an HTML DOM object)?

Because that would lead to many small nasty bugs on different elements.  
Having it on a dedicated element makes it easier to implement which is a  
big plus given the interoperability issues we have with <canvas> today  
(although, like CSS, it's still usable).


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Wednesday, 1 August 2007 00:50:47 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:36 UTC