W3C home > Mailing lists > Public > whatwg@whatwg.org > May 2006

[whatwg] canvas

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 16 May 2006 11:16:30 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0605161114390.21459@dhalsim.dreamhost.com>
On Wed, 20 Apr 2005, dolphinling wrote:
> 
> I think I agree with Sjoerd here. Changing canvas to be applied to the 
> img/object elements instead of its own element would be much more 
> semantic, and would also provide better fallback.

Unfortunately, we are constrained by previous implementation work here 
(and we were even when the issue was originally raised, sorry for taking 
so long to answer it).

However, even if we weren't, IMHO it makes good sense to use different 
elements for different things. If the overloading of <object> has taught 
us anything, it's that putting multiple features on one element leads to 
massive interoperability failures. It has taken years to get <object> 
anywhere near usable, and it still isn't fully usable in all 
implementations. Adding yet more features to it is not a good plan, IMHO.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 16 May 2006 04:16:30 UTC

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