Summary Summary: Remove the meter element. Rationale The rationale given by the HTML5 editor[1] for keeping the meter element is: Rationale: We have to have <meter> if we have <progress> because otherwise people will abuse <progress> to get gauges, leading to bad accessibility. It’s difficult to write a change proposal asking to remove the meter […]
Summary: Split the material related to the browsing context into a separate specification, reducing the existing HTML5 to covering HTML, XHTML, and the DOM, only. Rationale The following is my initial request that led to this issue[1] Currently the HTML5 specification contains a section, Section 6, devoted specifically to browsers. The section also notes that […]
Categories
Web spec goulash
The biggest mistake associated with the HTML5 specification is also the only mistake that can’t be corrected: the charter. The charter allowed the group to create an HTML and XHTML serialization, as well as an associated DOM. Unfortunately, the interpretation of this charter was such that all three tasks have been combined in one document, […]
Over time as I looked at several of the new elements in HTML5, I saw a trend: many of the elements are single purpose derivations of popular, and commonly occurring, JavaScript and CSS applications. Consider the following list: the progress element the meter element the hidden attribute the details element the telephone input type the […]
Summary Summary: Replace too-simple and somewhat odd example table and verbose text unrelated to the table element, with one example table, derived from real world data that best demonstrates the table element. Refocus the text specifically on the table element. Rationale In the bug[1] related to this issue, the HTML5 Editor’s rationale for not make […]