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 […]
Summary Remove the srcdoc attribute. Rationale The original bug report for removing srcdoc provided the following change request[1]: This recent entry does not have universal acceptance, and the group was still discussing it when the editor added it to the specification. The supposed use case for this attribute is weblog comments, but concerns about HTML […]
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 […]