Some useful out of box functionality, but setting forth a pattern for having HTML elements on the page talk to each other (without that talking being in js)!
Starting place/vast boon for a #ViewSource #MalleableSystems web.
Oh no! Philosophically I believe reflecting what is onto the page to be the highest most important calling, that there is a compelling & vital #ViewSource ideology that Human Computer Interaction #hci has yet to discover & which webizens ought be compelled to chase.
#ViewSource. View source is my priority by country miles.
How much does the HTML source show what the page does? How much of the page's behaviors can be altered via HTML? Maximize the page's expression of itself!
It feels like so much of the web is driven by js, is code. It's fine I guess for an org?
But it's so suboptimal for the #ViewSource world, trying to learn how an app boot and runs. The page's html doesn't really speak for itself: it's a mere transient incidental disposal artifact of the code.
Pretty sure Google Calendar would render just fine in IE4, just saying. #viewsource
Registration to Jsconf2010 is fun : http://jsconf.us/2010/ -> hint : #viewsource and use a good JS console :) #jsconf
