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 8702 - "Within a single dl element, there should not be more than one dt element for each name" - intention of this requirement is unclear; is this a machine-checkable requirement, or a requirement on semantics? What will be used to compare "name"s, textContent
Summary: "Within a single dl element, there should not be more than one dt element for...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-11 04:40 UTC by contributor
Modified: 2010-10-04 13:59 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-01-11 04:40:10 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-dl-element

Comment:
"Within a single dl element, there should not be more than one dt element for
each name" - intention of this requirement is unclear; is this a
machine-checkable requirement, or a requirement on semantics?  What will be
used to compare "name"s, textContent, innerHTML, or anything else?

Posted from: 220.210.139.236
Comment 1 Ian 'Hixie' Hickson 2010-02-06 00:37:05 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 a SHOULD because of this vagueness. :-) I think in most cases it's clear if this is being followed or not. It's not easily machine-checkable.