- From: <bugzilla@jessica.w3.org>
- Date: Tue, 12 Oct 2010 08:25:37 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10981 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |ian@hixie.ch Resolution| |WONTFIX --- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-10-12 08:25:37 UTC --- 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: Rejected Change Description: no spec change Rationale: It's not so much that it can't contain headings, so much as it has to only contain phrasing content, much like <legend> or <p>, or, indeed, <h1>. In the example given, you can just use <details> as is. Just style it to look like in the mockup using CSS. It's all semantically fine, because the whole point of <summary> is that it's the "heading" for the contents of the <details>. :-) (It's a little suboptimal in that really <details> should be used to hide stuff that is summarised in <summary>, not to create a section that can be closed, the latter is really more presentation. But that's somewhat splitting hairs.) -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 12 October 2010 08:25:39 UTC