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 12897

Who When What Removed Added
xn--mlform-iua 2011-06-06 20:15:50 UTC CC xn--mlform-iua
xn--mlform-iua 2011-06-06 21:11:51 UTC Attachment #994 Attachment filename xhtml.html.koi8-r.xhtml file.html.koi8-r.xhtml
Attachment #994 Attachment description UTF-8 encoded HTML-compatible XHTML file with BOM, served as 'Content-Type: text/html; charset=koi8-r' Polyglot file with BOM, served as 'Content-Type: application/xhtml+x; charset=koi8-r'
xn--mlform-iua 2011-06-06 21:12:16 UTC Attachment #994 Attachment description Polyglot file with BOM, served as 'Content-Type: application/xhtml+x; charset=koi8-r' Polyglot file with BOM, served as 'application/xhtml+x; charset=koi8-r'
xn--mlform-iua 2011-06-06 21:12:53 UTC Attachment #995 Attachment filename xhtml.html.koi8-r.html file.html.koi8-r.html
hsivonen 2011-06-07 05:14:24 UTC CC hsivonen
julian.reschke 2011-06-07 12:45:39 UTC CC julian.reschke
ian 2011-06-16 18:06:41 UTC CC ian
Assignee ian contributor
Severity normal major
mike 2011-08-04 05:16:46 UTC Component HTML5 spec (editor: Ian Hickson) LC1 HTML5 spec (editor: Ian Hickson)
xn--mlform-iua 2011-08-11 19:18:27 UTC Summary UTF-8 BOM should trump users and/or HTTP (Encoding sniffing algorithm) In some parsers, UTF-8 BOM trumps the HTTP charset attribute (Encoding sniffing algorithm)
hsivonen 2011-12-02 08:26:26 UTC Status NEW RESOLVED
Resolution --- WONTFIX

Back to bug 12897