What’s not in HTML 5?
In Mark’s latest installment of This Week in HTML 5 he delves into what ISN’T in the spec:
It has been suggested (1, 2, 3, &c.) that HTML 5 is trying to bite off more than it can metaphorically chew. It is true that it is a large specification, andit might benefit from being split into several pieces. But it is not true that it includes everything but the kitchen sink.
For example, HTML 5 will not
- deprecate
<textarea>- allow arbitrary markup in
<option>- include an
<altinput>element (reference)- allow authors to localize the “Browse” button that represents a file input control
- allow authors to localize the open-file dialog that opens in response to activating a file input control
- mandate that browsers display a progress bar during file upload
- limit the number of selected checkboxes or options in a web form
- allow web authors to specify a regular expression constraint on a
<textarea>- support form controls associated with more than one form
- change the default type of
<button>- allow web authors to mark form fields as auto-tabbing
- support form seeding
- rename the
HTMLCollection.lengthattribute to.count- expose a native JSON parser for web content
- support client-side includes
- try to compete with Docbook
November 17th, 2008 at 2:52 pm
[...] VIEW ORIGINAL ARTICLE [...]