Bug 10155
| Summary: | CSS2: @charset is not supported | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Patrik Weiskircher <pat> |
| Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | ap |
| Priority: | P2 | ||
| Version: | 419.x | ||
| Hardware: | Mac | ||
| OS: | OS X 10.4 | ||
| URL: | http://amd.co.at/pat/webkit/ | ||
Patrik Weiskircher
If you set the charset encoding of a external CSS file using either one of the following methods, it gets ignored:
@charset in the css file
Content-Type: text/css; charset=utf-8 or
Content-Encoding: utf-8
As soon as you specify the charset in the <link> itself, it works as expected.
Please see the above mentioned URL.
With nonworking.html, the <link> does not specify the charset, but test.css starts with '@charset "utf-8";' and the Content-Type is set to 'text/css; charset=utf-8'.
working.html references the same test.css, but specifies the charset in the <link>.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
Specifying a charset in Content-Type works in current WebKit, you can verify this with a nightly build from <http://nightly.webkit.org>.
Do any browsers honor a charset specified in the Content-Encoding header? The only registered options are gzip, compress, deflate and identity: <http://www.iana.org/assignments/http-parameters>.
Spec for @charset: <http://www.w3.org/TR/CSS21/syndata.html#x60>. Renaming the bug to track this single issue.
Alexey Proskuryakov
Fixed in bug 5620, r16175.