8096 2009-10-27 22:56:21 +0000 <link>'s "type" attribute should be allowed to appear multiple times and/or should allow for a space separated list of advertised types, such that clients can request them via the Accept: header. 2010-10-04 14:57:35 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED NEEDSINFO http://www.whatwg.org/specs/web-apps/current-work/#default-media NE P3 normal LC 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking samj public-html-bugzilla oldest_to_newest 29141 0 contributor 2009-10-27 22:56:21 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#default-media Comment: <link>'s "type" attribute should be allowed to appear multiple times and/or should allow for a space separated list of advertised types, such that clients can request them via the Accept: header. Posted from: 84.75.177.17 30156 1 ian 2009-12-15 23:41:22 +0000 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: I don't understand. Could you elaborate? What's the use case? What would the UA processing requirements be? What problem does it solve? 30159 2 samj 2009-12-15 23:47:31 +0000 Linked resources may have multiple representations and allowing for "type" to be multi-valued would allows servers to advertise, and clients to discover, the available representations (which could be specified in subsequent requests by way of the Accept: header). 30161 3 samj 2009-12-15 23:52:36 +0000 *** Bug 8095 has been marked as a duplicate of this bug. *** 30363 4 ian 2010-01-04 09:27:11 +0000 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: Could you describe a situation in which a user today would run into a problem, and where this proposal solves that problem? I'm having trouble understanding the proposal.