This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section: http://www.whatwg.org/specs/web-apps/current-work/#metadata-content-0 Comment: A summary table of the types of content and what elements belong to each would be helpful Posted from: 64.134.222.102
Do you have any suggestions for what these tables should look like? I'm not sure how best to present this information.
*** Bug 8944 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > Do you have any suggestions for what these tables should look like? I'm not > sure how best to present this information. > A table with three columns would work: category, elements, exceptions. For instance, the "flow content" category would have "Flow Content", followed by: a abbr address area article aside audio b bdo blockquote br button canvas cite code command datalist del details dfn div dl em embed fieldset figure footer form h1 h2 h3 h4 h5 h6 header hgroup hr i iframe img input ins kbd keygen label link map mark math menu meta meter nav noscript object ol output p pre progress q ruby samp script section select small span strong style sub sup svg table textarea time ul var video text Followed by: area (only when a descendent of the map property), link (only when the itemprop property is present), style (only when the scoped property is present). I chose Flow Content to illustrate, because it is complex, but most of the sections are limited to a few elements, and table presentation would be helpful (imho).
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, 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 Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments.
Checked in as WHATWG revision r4797. Check-in comment: First crack at an index table for the categories. If you have any ideas of how better to arrange this, please let me know. http://html5.org/tools/web-apps-tracker?from=4796&to=4797