The audience was mostly people who work with creating Web sites.
The discussion afterwards was interesting, but it wasn't recorded and I can't recall all the questions, unfortunately. These are the ones I can recall for now however:
When will HTML5 actually be used by web developers?
That's up to you.
When will HTML5 be finished? What is the time line?
That's up to how fast browser vendors implement it. The W3C HTML WG's roadmap says that HTML5 will advance to Recommendation by 2010, but I don't think it is realistic to think that browser vendors will have implemented everything completely and correctly by then. Around 15 years is more realistic, however that doesn't mean that you will have to wait 15 years until you can use HTML5.
What is the advantage of using Web Forms 2.0 instead of using HTML4 forms + JavaScript?
Less work for authors, and a better user experience for users. For instance, using an <input type=email> means that the author doesn't have to write JS to validate that it is a correct email address on the client side, and the user can pick emails from her address book (something that is impossible to implement with JS).
Can you style the new form controls with CSS?
They can probably be styled to the same extent that existing form controls can be styled. The icon in the email control is added by Opera when the form control is styled in some way (I just set a white background color to make the icon appear.)
Can you style or modify the form's error messages?
I'm not sure if you can style them, however you can change the text with JS or override the error reporting mechanism and use your own custom mechanism with JS.
Is it true that HTML5 allows <font>?
No, authors are not allowed to use <font>. However, WYSIWYG editors are allowed to emit <font>. WYSIWYG editors have to identify themselves with a <meta> element. This has received a lot of feedback though and might be changed.
Do you need to be consistent with the use of /> vs. >?
No.
If you don't specify what version of HTML a document is, how can you redefine the behavior of an element later in HTML6?
You don't. Browsers treat all HTML documents the same way, regardless of what version they declare themselves of being. A good example of this is <plaintext>, which has been deprecated since HTML 1.0, and is still supported in all browsers even if you declare an HTML4 doctype.
Does HTML5 deprecate anything?
Nothing is actually deprecated, however some things are forbidden altogether. For example the <u> element is not allowed to be used in conforming HTML5 documents. Browsers will continue to support it, however.
Can html5lib parse any tag soup?
Yes.
Does that mean that you can convert any old HTML document to XML by feeding it through html5lib?
Yes.
Can you use the <svg> tag in HTML5?
No, you can't use namespaces in HTML5. You can however embed SVG in XHTML5, since it's simply XML.
This entry was posted
on Thursday, May 24th, 2007 at 18:21 and is filed under WHATWG.
You can follow any responses to this entry through the RSS 2.0 feed.
Both comments and pings are currently closed.
4 Responses to “Presentation: How HTML5 can be used today”
[...] Original post by Simon Pieters Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages. [...]
Does that mean that you can convert any old HTML document to XML by feeding it through html5lib?
Yes.
As was pointed out in IRC, this is not quite correct. Any old HTML document can be parsed into a DOM, but any DOM cannot be serialized as XML 1.0. For instance, XML 1.0 puts restrictions on what characters can be used in attribute names. It is also not the case currently that any conforming HTML5 document can be reserialized as XML 1.0, because HTML5 allows for characters in data that are forbidden in XML 1.0, such as U+000C FORM FEED.
May 24th, 2007 at 18:34
[...] Original post by Simon Pieters Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages. [...]
May 24th, 2007 at 21:27
As was pointed out in IRC, this is not quite correct. Any old HTML document can be parsed into a DOM, but any DOM cannot be serialized as XML 1.0. For instance, XML 1.0 puts restrictions on what characters can be used in attribute names. It is also not the case currently that any conforming HTML5 document can be reserialized as XML 1.0, because HTML5 allows for characters in data that are forbidden in XML 1.0, such as U+000C FORM FEED.
July 20th, 2007 at 09:26
HTML5 is arising, well I’m strained how long it will take until it’ll be supported by all browser vendors (exspecially by these M$ guys)…
August 23rd, 2007 at 17:47
Where can one find more articles about HTML5?