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 11610 - The abbr element I suggest to add the for attribute, for abbreviations and acronyms defined inline. Some solution proposals: 1. <abbr>W3C</abbr> (<title for="W3C">World Wide Web Consortium</title>) 2. <abbr>CC</abbr> (<dfn for="CC">Creative Commons</dfn>)
Summary: The abbr element I suggest to add the for attribute, for abbreviations and ac...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
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-12-27 12:50 UTC by contributor
Modified: 2011-08-04 05:13 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2010-12-27 12:50:15 UTC 
Specification: http://dev.w3.org/html5/spec/Overview.html
Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#top

Comment:
The abbr element

I suggest to add the for attribute, for abbreviations and acronyms defined
inline. Some solution proposals:
1. <abbr>W3C</abbr> (<title for="W3C">World Wide Web Consortium</title>)
2. <abbr>CC</abbr> (<dfn for="CC">Creative Commons</dfn>)
Where the for content is equal to the abbr content, always shorter as an
abbreviation or an acronym. 

Posted from: 78.13.251.223
Comment 1 Ian 'Hixie' Hickson 2011-02-11 22:47:42 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: Did Not Understand Request
Change Description: no spec change
Rationale: What problem does this solve?
Comment 2 Michael[tm] Smith 2011-08-04 05:13:07 UTC 
mass-move component to LC1