This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Cynthia: Im not sure what this sentence means: The details element represents a disclosure widget from which the user can obtain additional information or controls. After reading through the section, it seems to be for those more info popups. There is no discussion of what the default rendering looks like. I think it looks like this <details> <dt>More Info</dt> <dd> <img> <p>blah blah blah</p> </dd> </details> Would render as just More Info. The author would have to write script to toggle the open attribute. This should have a built-in tabstop (not specified) and built-in toggling behavior (not specified). The default rendering should be specified. For example, does an open details section cause the page to reflow? Cynthia: Can the <dt> and the <dd> contain any arbitrary tags?
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: Partially Accepted Change Description: see diff given below Rationale: I've tried to clarify these details, in particular by adding an example. Most of the points raised are already explained in the <details> section, though, as far as I can tell. In particular, no scripting is involved, and the content models are fully defined in the section's header.
Checked in as WHATWG revision r4541. Check-in comment: Add an example of <details>. http://html5.org/tools/web-apps-tracker?from=4540&to=4541
Per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html, the HTML A11Y TF does not plan to formally work on this issue at this time. This does not mean the TF has no interest in it, but does not have immediate plans to work on it. The TF may review the issue in the future.