This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Back to bug 18338
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| ian | 2012-08-25 16:47:39 UTC | CC | ian | |
| ian | 2012-10-31 22:27:01 UTC | CC | hsivonen | |
| ian | 2012-11-01 22:32:33 UTC | Status | NEW | RESOLVED |
| Resolution | --- | LATER | ||
| Summary | Include a document-conformance requirement for valid encoding information in the Content-Type headers with a charset param | text/html MIME type definition should require that charset="" value be valid and correct | ||
| Whiteboard | registry | |||
| ian | 2013-01-05 01:46:46 UTC | Status | RESOLVED | REOPENED |
| Resolution | LATER | --- | ||
| ian | 2013-03-06 22:09:42 UTC | Target Milestone | Unsorted | 2014 Q1 |
| ian | 2013-04-12 22:42:19 UTC | Status | REOPENED | NEW |
| ian | 2014-05-07 17:36:03 UTC | Target Milestone | 2014 Q1 | Unsorted |
| annevk | 2015-09-02 05:46:08 UTC | CC | annevk | |
| Summary | text/html MIME type definition should require that charset="" value be valid and correct | Registries (IANA): text/html MIME type definition should require that charset="" value be valid and correct | ||
| hoangminh120814 | 2016-07-20 22:58:02 UTC | OS | other | All |
| annevk | 2017-07-21 11:12:36 UTC | Resolution | --- | WORKSFORME |
| Status | NEW | RESOLVED |
Back to bug 18338