This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
All user agents which uses the META content-language for setting a pragma set default language (at least Konqueror, Webkit, Chrome, Mozilla/Gecko, IE, Opera) give precedence to the last META declaration. HTML4 also defines the same pattern for the default-style META declaration - and that is also how at least Mozilla and Webkit implement it. Therefore, HTML5 should say that it is the last META content-language declaration which takes precedence. Doing so is congruent with reality.
This bug alsor relates to bug 9417 and 9420. The goal with all these bugs is to make the last META content-language element the *end station*. Only if there is no META content-language element should the User Agent ask what the content-language header from the server says. Also see the pattern which HTML4 sets - bug 9409. Quoting HTML4: 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. [[
Created attachment 859 [details] Test case for the emptystring inside META content-language (and META default-style) The test case for how the emptystring inside META content-language (and empty string inside META default-style) is interpreted in different user agents is also available here: http://www.malform.no/testing/html5/content-language-empty-string/
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: Unless you are aware of real Web content that is negatively affected by this change, the UA change cost is worth it as part of simplifying the way pragmas are handled.
Change Content-Language pragma to obeying the last pragma, not the first, as this is closer to what Firefox, IE9, and WebKit do. This was applied to the WHATWG spec in https://github.com/w3c/html/commit/184c4d2452b16f787fcc98bebc682ad3a3d155bb
*** Bug 18883 has been marked as a duplicate of this bug. ***
Thanks Lief! 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: Patch applied https://github.com/w3c/html/commit/184c4d2452b16f787fcc98bebc682ad3a3d155bb Rationale: adopted from WHATWG