W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > April 2010

[Bug 9422] Mozilla and <META http-equiv="content-language" content="<emptystring>" >

From: <bugzilla@jessica.w3.org>
Date: Wed, 14 Apr 2010 06:37:09 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1O1wDl-00078c-Hn@jessica.w3.org>

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
             Status|REOPENED                    |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #7 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-04-14 06:41:04 ---
> I must make you aware that the empty string is not an error in
> HTML5. At least not as I and Validator.nu reads the specification. 

The spec says "the content attribute must have a value consisting of a valid
BCP 47 language tag" and the empty string (or indeed a string of spaces) is not
a valid language tag according to BCP 47.

> > useful
> > only for a very dubious workaround of a bug with the lang="" processing in
> > legacy UAs.
> Just change your algorithm so that it only looks at the last META, and I can
> cut it down to only 2 lines. Which means that there would only be one "dubious"
> line.

The whole use of Content-Language as any kind of hack to work around two bugs
(the lack of support for lang="" and the misinterpretation of HTTP's
Content-Language header) is dubious. Making it two lines instead of three makes
no improvement.

> Please also note that being able to cancel the HTTP header is useful in any
> user agent that is able to read the HTTP headers. (Currently also coves IE.)

You can "cancel" this misuse of the HTTP header using the lang="" attribute.

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:

Status: Rejected
Change Description: no spec change
Rationale: No new information.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 14 April 2010 06:41:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:16 UTC