W3C home > Mailing lists > Public > public-html@w3.org > December 2011

[Bug 15359] New: Make BOM trump HTTP

From: <bugzilla@jessica.w3.org>
Date: Thu, 29 Dec 2011 14:20:45 +0000
To: public-html@w3.org
Message-ID: <bug-15359-2495@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15359

           Summary: Make BOM trump HTTP
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: annevk@opera.com
         QAContact: public-html-bugzilla@w3.org
                CC: hsivonen@iki.fi, mike@w3.org,
                    public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org, adrianba@microsoft.com,
                    Ms2ger@gmail.com, VYV03354@nifty.ne.jp,
                    travil@microsoft.com


In Trident and WebKit the octet sequences FF FE, FE FF, and EF, BB, BF at the
start of a resource are considered more important than anything else when it
comes to determining the encoding of the resource.

http://kb.dsqq.cn/ is an example of where this creates a problem for
non-WebKit/Trident implementations.

I think throughout the platform (HTML, XHR, File API, CSS) we should implement
the WebKit/Trident strategy with respect to the BOM.

(I created a new bug rather than reopening bug 12897 as that bug has a lot of
noise.)

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Friday, 30 December 2011 10:26:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:42 GMT