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

[Bug 9628] Algorithm for detecting the charaset="" parameter.

From: <bugzilla@jessica.w3.org>
Date: Wed, 29 Sep 2010 02:00:35 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1P0lyF-0007O4-RA@jessica.w3.org>

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

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

--- Comment #11 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-09-29 02:00:34 UTC ---
None of these tests are testing what the spec is doing here. This has nothing
to do with HTTP. If you click the name of the algorithm you will get a list of
the places that use this.

Since I was looking at this part of the spec, though, I went ahead and redid a
round of testing to see how the browsers were doing today. I didn't have IE
handy, but looking at the other major browsers, it looks like all but Firefox
skip past unknown parameters, so I've changed the spec to support that.

WebKit and Opera's main sources of bugs are that they do extra trimming that
the spec doesn't expect. Both also do weird things with unmatched single quotes
that they don't do with unmatched double quotes, which is weird. WebKit also
seems to have trouble with "&quot;". Gecko doesn't drop charset declarations
when they have unmatched quotes, but otherwise seems to match the spec. I
haven't changed the spec to match these quirks, since it's not clear whether
pages depend on them or not.

My test suite is here, in case anyone can test IE9:

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 was provided by the reporter since the rejection
in comment 4.

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, 29 September 2010 02:00:37 UTC

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