6842 2009-04-22 05:18:30 +0000 make it possible/easy to link to tables documenting <input> element keywords/states and attributes/methods 2010-10-04 14:00:09 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All CLOSED FIXED P2 enhancement --- 1 mike ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 24902 0 mike 2009-04-22 05:18:30 +0000 There are a couple of very useful tables in the main section of the spec that documents the <input> element: one table listing details about <input> keywords and states, and one listing details about which attributes and methods can be used with which particular states. It would be useful if those tables could be directly referenced/linked to using URLs with fragment IDs. So maybe either: 1. put the tables into titled subsections of their own; or 2. add titles/<caption>s to the tables; or 3. add IDs to the tables themselves Wrapping each table in a titled subsections of it own would seem to me best, since that will also cause them to appear in the TOC. 25411 1 ian 2009-06-01 21:57:25 +0000 Added id=""s. I couldn't work out how to make sections work while still being consistent with the spec's writing style. 33100 2 mjs 2010-03-14 14:48:05 +0000 This bug predates the HTML Working Group Decision Policy. If you are satisfied with the resolution of this bug, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html This bug is now being moved to VERIFIED. Please respond within two weeks. If this bug is not closed, reopened or escalated within two weeks, it may be marked as NoReply and will no longer be considered a pending comment.