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 9409 - Spec that the last 'default-style' (whether http-equiv or http) takes precedence
Summary: Spec that the last 'default-style' (whether http-equiv or http) takes precedence
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://dev.w3.org/html5/spec/semantic...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-05 12:26 UTC by Leif Halvard Silli
Modified: 2010-10-04 14:57 UTC (History)
5 users (show)

See Also:


Attachments

Description Leif Halvard Silli 2010-04-05 12:26:48 UTC
The spec now says:

]]
Default style state (http-equiv="default-style")
This pragma sets the name of the default alternative style sheet set.

If the meta element has no content attribute, or if that attribute's value is the empty string, then abort these steps.

Set the preferred style sheet set to the value of the element's content attribute. [CSSOM]
[[

Please adobt what HTML4 says - namely, that the last META declaration and/or HTTP header takes presdence.
http://www.w3.org/TR/html4/present/styles#h-14.3.2

]]
If two or more META declarations or HTTP headers specify the preferred style sheet, the last one takes precedence. HTTP headers are considered to occur earlier than the document HEAD for this purpose.
[[
Comment 1 Leif Halvard Silli 2010-04-06 17:51:32 UTC
A test of how UAs react to META default-style declaration when its value is the empty string:

http://www.malform.no/testing/html5/content-language-empty-string/
Comment 2 Ian 'Hixie' Hickson 2010-04-13 01:24:59 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: This is an intended simplification. There is minimal content using this so it doesn't much matter if we change the way duplicates are handled. (They're invalid now anyway.)