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 7449 - editorial: hyperlinked "represents" on the id attribute definition
Summary: editorial: hyperlinked "represents" on the id attribute definition
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 trivial
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Keywords: NoReply
Depends on:
Reported: 2009-08-27 19:58 UTC by Shawn Medero
Modified: 2010-10-04 13:58 UTC (History)
3 users (show)

See Also:


Description Shawn Medero 2009-08-27 19:58:18 UTC
Per Hixie's request,, here's an example of a hyperlinked "represents" on an attribute definition. "The id attribute _represents_ its element's unique identifier (ID)."

The represents is hyperlinked to a definition that says: "In the absence of style-layer rules to the contrary (e.g. author style sheets), user agents are expected to render an element so that it conveys to the user the meaning that the element represents, as described by this specification"  -- that doesn't make a lot of sense to me when the spec is talking about an attribute.
Comment 1 Maciej Stachowiak 2010-03-14 14:50:18 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:

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.
Comment 2 Shawn Medero 2010-04-19 15:49:12 UTC
Fairly certain this bug was addressed back in August 2009 and then that section undertook a few rewrites anyway... I'm sure this is resolved. (The current spec text doesn't exhibit the original problem either.)