This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7509 - Consider <dl type="dialog"> instead of <dialog>
Summary: Consider <dl type="dialog"> instead of <dialog>
Status: VERIFIED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://dev.w3.org/html5/spec/Overview...
Whiteboard:
Keywords: NE, NoReply
Depends on:
Blocks:
 
Reported: 2009-09-06 22:47 UTC by Leif Halvard Silli
Modified: 2010-10-04 14:46 UTC (History)
4 users (show)

See Also:

Attachments

Description Leif Halvard Silli 2009-09-06 22:47:19 UTC 
Some argument for choosing <dl dialog> or <dl type="dialog"> instead of <dialog>:

(1) Breakability:

[Relates to In IE, Firefox, Opera and Webkit ]

When used inside <dl> it is OK to not close <dt> and <dd>. But inside a new element, such as <dialog>, legacy (aka current) user agents will make the first element after </dialog> in the following example a child of the preceding <dd>:

    <dialog><dt>Name<dd>Word</dialog>
    <p>Paragraph.

Same goes for the following example, except that it becomes a child of the unclosed <p>

    <dialog><dt>Name<dd>Word <p>Paragraph.</dialog>
    <span>span</span>

(2) Bug 7508: There is no reason to have different rules for where <dt> is permitted when used inside <dialog> and when used inside <dl>.

(3) HIstory: HTML 4 reccommeds dialogs inside <dl>

(4) Future: As HTML developes, one might want to use <dl> for other types of lists as well - an attribute solution sets a precedence for such extensions.
Comment 2 Ian 'Hixie' Hickson 2009-09-15 11:05:32 UTC 
I nuked <dialog> altogether, per bug 7548.
Comment 3 Maciej Stachowiak 2010-03-14 14:50:43 UTC 
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.