Month: March 2010

Summary Summary: Eliminate the Details element, completely. Do not spin it off into another specification, or wrap it in a specification of its own. Rationale The HTML5 specification states: The Details represents a disclosure widget from which users can obtain additional information or controls. Two examples of the use of Details are given: one where […]

Summary Summary: Remove the progress element. Rationale In the bug associated with this issue[1], the HTML5 editor, Ian Hickson wrote as rationale for turning down the change request: Rationale: <progress> fixes a serious accessibility problem with dynamic apps, and accessibility is important. I have to make a guess about what serious accessibility problem progress solves, […]

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 […]

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, […]