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 12736 - Clarify if the sizes attribute is valid without rel=icon
Summary: Clarify if the sizes attribute is valid without rel=icon
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-24 11:09 UTC by Henri Sivonen
Modified: 2011-08-10 01:21 UTC (History)
4 users (show)

See Also:


Attachments

Description Henri Sivonen 2011-05-24 11:09:13 UTC
Please clarify whether the presence of the sizes attribute on the link element is valid regardless of the rel keywords. (Please note that if you make it keyword-dependent, the registration mechanism needs to support the registration of apple-touch-icon with sizes, so it would be easier not to couple the validity of sizes to the rel keywords.)
Comment 1 Michael[tm] Smith 2011-08-04 05:01:38 UTC
mass-moved component to LC1
Comment 2 Ian 'Hixie' Hickson 2011-08-09 23:24:38 UTC
Can I just couple it to rel=icon? It's ok if new rel values that need sizes="" can't be registered in the wiki but have to be registered in the spec, since they're so rare (one every twenty years so far).
Comment 3 Ian 'Hixie' Hickson 2011-08-10 01:21:33 UTC
In fact the spec already says "The sizes attribute is used with the icon link type. The attribute must not be specified on link elements that do not have a rel attribute that specifies the icon keyword."

If that's not good enough, reopen the bug and we can study this further, but it seems to address the issue you raised.


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: Accepted
Change Description: no spec change
Rationale: This seems to have been fixed already.