9270 2010-03-18 15:13:49 +0000 Add <dialog> back 2010-10-04 14:55:44 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#conversations P3 normal LC 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 33672 0 contributor 2010-03-18 15:13:49 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#conversations Comment: I think this specification is a big step backwards. I don't know if it technically qualifies as “tag soup”, but it sure feels like it. Semantically, a <dl> makes more sense, and moreover I think the <dialog> element (removed during current ongoing HTML5 work) was an EXCELLENT element that solves a very common use case. If HTML5 attempts to formalize already-common practices on the Web, it should provide a <dialog> element. Marking up a conversation as defined in the specification—at least, the one I’m commenting on right now…I hope the version is preserved—it seems contradictory to resort to a group of mixed generic <p>s, <time>s, and <b>s when the spec has gone out of its way to formalize other widespread conventions like <article>. PLEASE, bring back <dialog>! Posted from: 129.2.139.195 34265 1 ian 2010-03-31 20:28:23 +0000 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: As much as I agree with you, <dialog> as it stood was not good enough for most people to like it. I imagine we'll probably revisit this at some future point, but for now it's probably best to just wait until browsers have caught up with all the new stuff we _have_ added, and then add a proper solution once things have calmed down again.