In talking with one of the Mikes at the Dayton Web Standards Meetup about what topics people would like to hear at an upcoming meeting, I shot off an email half-thinking, “well, I would like a talk on HTML5 and CSS3.”
I’m not exactly sure what his response was, but at the next meetup I was standing in front of about twenty people wanting to hear what I found out about HTML5.
That Mike sure is a sly one. Well, one of them, at least.
To be honest, I wasn’t too thrilled about the prospect of HTML5. I’m a little weary of anything still in the larval stage of Web development after getting bitten badly by the poor Netscape Navigator 4 betas.
But, as I dove into a little bit of HTML5 and what bleeding edge browsers that support the unfinsihed spec. Below are my slides from the presentation that can help other people who were as clueless as I was about HTML5.
What we really need is an HTMLTextArea control, that support entering WYSIWYG formatted HTML, help us combat XSS and Word formatting. In this new work of user generated content I think that this has to be top priority.
no audio?
Wow the usability of that embedded slide widget is awful.
You should check out this great invention called HTML, it’s great for presenting information on the web, unlike static images. Maybe then the links would work reliably, and users could copy and paste text.
@Eduardo Molten That’s a good idea, but I think with a talented programmer you could overcome both those problems on the server-side and client-side.
@rick I personally didn’t record any audio for the presentation. But I might do a recording on my own and add it in later.
@Cameron I’ve updated the settings on the slides. You can now download a copy of the presentation.
Hi Christopher,
Loved the slides. Did anyone record you?
AL
Well, I guess that *all* proposed changes for HTML5 could be overcome by talented programmers.
@Eduardo Molteni: Great idea; couldn’t browser developers already do that with the plain old textarea? After all, the good ones have already enhanced it with spell-checking, that would just be a further (well, quite a *bit* further) step.
SECTION, ARTICLE and ASIDE elements? Good heavens no! I agree on adding more semantics to the web, but please dont start with this, the web has too much variation for this. I agree with a lot with things like CANVAS and a whole lotta CSS3 stuff, but I really dont see anything useful in adding ARTICLE elements. Please get more focused on RDFa or something…
(nothing against this post tho, this is just the first time I see an outline of HTML5)