Comments on: HTML5, who is bad enough to take on canvas?

By: Elroy Bridge

Elroy Bridge — Tue, 22 Dec 2009 21:17:43 +0000

I would like to thank you for the endeavors you have made in composing this article. I am hoping the same best work from you in the future as well. In fact your fanciful writing abilities has inspired me to start my own blog now. Actually the blogging is spreading its wings rapidly. Your write up is a fine instance of it.

By: Peter Kingsbury

Peter Kingsbury — Sun, 13 Dec 2009 02:44:17 +0000

My first impulse, once introduced to HTML5 Canvas, was tile-based RPGs. Take a look at http://tge.stormwarestudios.com/ and let me know what you think.

By: HTML5 – jetzt neu mit gebremstem Schaum

HTML5 – jetzt neu mit gebremstem Schaum — Sat, 12 Sep 2009 22:04:51 +0000

[...] Nicole Sullivan: »HTML5, who is bad enough to take on canvas?« [...]

By: Nicole

Nicole — Fri, 11 Sep 2009 17:50:09 +0000

@Nicholas C. Zakas – the standards world moves at a glacial pace, this is both an advantage and an inconvenience. Thanks for the links, you made some good points.

By: Nicholas C. Zakas

Nicholas C. Zakas — Sun, 06 Sep 2009 06:48:15 +0000

Funny, this post made me go dig up some of my posts on HTML5:
http://www.nczonline.net/blog/2007/12/06/what-i-d-like-to-see-in-html-5/
http://www.nczonline.net/blog/2008/02/28/thoughts-on-html-5/

I think you and I agree on a lot of the points (funny that a lot of those are still relevant now, in 2009, when my first post was in 2007).

@Mark – JavaScript isn’t for creating UI, it’s for defining UI behavior. The UI should be defined by HTML and scripted by JavaScript. The paradigms Nicole is talking about have pretty clear user experiences, tabs tend to work the same way regardless of who implements them and how. Think of a checkbox control – should I also have to make that from scratch? Common UI elements are already part of HTML, we just need more of them so we don’t need to keep recreating the wheel. And just like the current UI elements, you’d be able to augment its behavior using JavaScript.

By: ø Web Forms and Opera 10 | i love and hate you all - On understanding people. Or at least trying to ø

Fri, 04 Sep 2009 16:33:47 +0000

[...] Stubbornella » Blog Archive » HTML5, who is bad enough to take on … [...]

By: Mark Perkins

Mark Perkins — Wed, 02 Sep 2009 12:22:36 +0000

"Practically every site in the known universe has toggle blocks, tabs, carousels, or accordion menus. I’d like to seen native browser support and CSS styling, so that these element incur no particular performance cost."

I'm sorry, but I have to say that I couldn't disagree with this more strongly about the above statement. I can only think of disadvantages (apart from, speculatively, performance) to having these elements implemented as native browser controls. How would we be able to fine tune their behaviour? What happens if I want a tabbed slider, not just a plain slider? What is the interaction model with these? How do we even get to decide what items (tabs, carosels etc) get included in the 'native' controls? What happens when someone invents a new 'widget' that becomes popular and widespread - Do we wait for HTML6 to include it? In my mind this sort of thing is exactly what javascript is for, and should stay well away from any kind of native browser implementation.

By: Nicole

Nicole — Tue, 01 Sep 2009 15:23:29 +0000

@hackepeter – Thanks! Let me correct that.

@James – It was a joke. I think you might be looking too deeply for meaning. What I did mean is that the standards, accessibility, and JS communities need to talk more. Canvas is in HTML5, with no way to use it accessibly (yet!)

@Audrey – Can you explain more?

By: hackepeter

hackepeter — Tue, 01 Sep 2009 14:53:53 +0000

“A conversation is an ugly way to use a DL, I mean, which speaker is the DT and which is the DD?”

the DT is the name of the Speaker and the DD is what the speaker says.

http://www.w3schools.com/tags/html5_dialog.asp

By: James Pearce

James Pearce — Tue, 01 Sep 2009 03:35:41 +0000

I am puzzled by your general assertion that ‘Javascript is to standards’ as ‘Ajaxian is to ALA’ as ‘canvas is to markup’ as ‘non-accessible is to accessible’.

These are mostly orthogonal vectors… I know you can’t be suggesting that all non-canvas code written by ALA readers is perfectly accessible And highly interactive web sites have had poor accessibility (and mobile suitability) long before canvas came along.

But in general I agree. My personal concern would not be about readership cliques and one tag per se, but about how to display *any sort* of ‘data via interactive charts and controls’ in a universally accessible way. Or even static charts!

This is an devilishly intriguing challenge, but on the whole unconnected to HTML5, I would have thought. No?