Linked by David Adams on Tue 23rd Sep 2008 00:57 UTC
From eWeek: "In a session billed as the browser wars up close and personal, key Microsoft, Mozilla and Google representatives spoke about the past present and future of the browser platform as they see it . . . one of the issues that stood out to me was that of developer discontent. When the Ajaxians opened up questioning to the audience, an attendee stood up and said Google's announcement of its new browser "was greeted with shock and horror," by him."
Permalink for comment 331142
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:
2005-11-10
Because Canvas gives you per-pixel control and fast animation that isn't possible with SVG. Canvas display is also limited to the canvas tag it's within whereas SVG can be placed anywhere.
Emulators have been written in Canvas/JS. You can't do that in SVG at all.
Canvas is for using for non-accessibility related issues. If I'm making a game in Canvas/JS instead of Flash; why should I care about accessibility when a blind person is not going to be able to see it anyway - regardless if it was Flash or Canvas.
A 3D rendering of a product is no more or less accessible as a Canvas / PNG, Flash or Java object as long as they have relevant ALT attributes &c.
SVG is for preserving document fidelity in the future as screen resolutions increase. Canvas is for making pretty, animated things.