- From: Maciej Stachowiak <mjs@apple.com>
- Date: Fri, 20 Mar 2009 18:47:06 -0700
- To: Charles McCathieNevile <chaals@opera.com>
- Cc: "John Foliot - WATS.ca" <foliot@wats.ca>, Wai-Ig <w3c-wai-ig@w3.org>, wai-xtech@w3.org, 'HTMLWG' <public-html@w3.org>, WebAIM Discussion List <webaim-forum@list.webaim.org>, Gawds_Discuss <gawds_discuss@yahoogroups.com>
On Mar 19, 2009, at 8:34 AM, Charles McCathieNevile wrote: > >> I propose that >> any instance of <canvas> that lacks at a minimum the 2 proposed >> mandatory >> values be non-conformant and not render on screen. The inclusion of >> this >> information should not be left to chance - the specification >> requires that some fallback content exist - and if it does not >> exist then the >> <canvas> element is incomplete, thus it should simply fail all >> users... > > I think that this is a non-starter. As explained in a narrower > follow-up, the penalty to browsers who do this means that mainstream > browsers simply won't, in all probability. I agree with Chaals on this. We would likely not be willing to stop rendering existing <canvas> content in Safari. Regards, Maciej
Received on Saturday, 21 March 2009 01:47:49 UTC