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 13797 - The "shortcut" keyword should be invalid. All reasons for this keyword are purely historic and it is semantically completely meaningless, hence it should not be valid today. Things like <iframe frameborder="0"> are not valid either.
Summary: The "shortcut" keyword should be invalid. All reasons for this keyword are pu...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: 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: 2011-08-16 20:19 UTC by contributor
Modified: 2011-08-16 20:25 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2011-08-16 20:19:47 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html
Multipage: http://www.whatwg.org/C#rel-icon
Complete: http://www.whatwg.org/c#rel-icon

Comment:
The "shortcut" keyword should be invalid. All reasons for this keyword are
purely historic and it is semantically completely meaningless, hence it should
not be valid today. Things like <iframe frameborder="0"> are not valid either.

Posted from: 87.225.253.173
User agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Comment 1 Anne 2011-08-16 20:25:30 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: We sometimes decide to allow certain legacy constructs on a case-by-case basis if they are in frequent use.