News for hackers. Stuff that matters.
Re:HTML 5 Canvas game by ruddzw on Friday March 13, 2009 @11:45AM (#514976)
It took me a while to realize that my default browser, Safari 3.2.1, doesn't support HTML 5 Canvas. I'm seeing a bowl and a logo. Graceful degradation, not so much.
Re:HTML 5 Canvas game by GHFigs on Friday March 13, 2009 @01:44PM (#515096)
Safari most certainly does support HTML5 Canvas. The canvas was originally introduced by Apple in 2004. (http://weblogs.mozillazine.org/hyatt/archives/2004_07.html#0...)
Re:HTML 5 Canvas game by ruddzw on Friday March 13, 2009 @07:41PM (#515453)
You're definitely right. I'm not so familiar with Canvas at all, so I assumed that since it didn't render, it wasn't supported. My main point was about the graceful degradation.
Re:HTML 5 Canvas game by mr_justin on Friday March 13, 2009 @02:58PM (#515185)
It's a proof of concept, and a darn good one, graceful degradation is unneeded.
Re:HTML 5 Canvas game by jdowdell on Friday March 13, 2009 @04:58PM (#515314)
People speak in binary on support for CANVAS, SVG, CSS etc -- "this browser has CANVAS support", "that browser doesn't have CANVAS support".

They should actually be speaking of "what level of CANVAS support", because there are different implementations among different browser brands, versions, and possibly operating systems. Whenever there's a common spec with multiple implementations, some solid conformance testing is vital before starting development.

(I'm not too concerned about the lack of "graceful degradation" here, because it's more of an enthusiast piece, "look what I can code", rather than something solid to deploy out to the general public. Different priorities.)

jd/adobe

Re:HTML 5 Canvas game by nickb on Friday March 13, 2009 @02:57PM (#515182)
Huh? You're completely wrong. How did this entry get 4 points?!

http://img24.imageshack.us/img24/2830/picture32s.png

Re:HTML 5 Canvas game by tectonic on Friday March 13, 2009 @03:27PM (#515218)
Re:HTML 5 Canvas game by rufo on Friday March 13, 2009 @04:10PM (#515268)
Same thing on Safari 3.2.1 here. Works fine with WebKit, though.