W3C home > Mailing lists > Public > www-international@w3.org > October to December 2012

[Bug 15359] Make BOM trump HTTP

From: <bugzilla@jessica.w3.org>
Date: Tue, 27 Nov 2012 08:22:02 +0000
To: www-international@w3.org
Message-ID: <bug-15359-4285-bx4cTkVeI3@http.www.w3.org/Bugs/Public/>

--- Comment #27 from Henri Sivonen <hsivonen@iki.fi> ---
(In reply to comment #22)
> The initial impetus for the change appears to be that Trident and WebKit
> supported different behaviour than the spec. If paving the cowpath is the
> main motivator, we have a problem, since Trident (in IE10) prioritises HTTP
> over BOM. 

But Firefox changed to give precedence to the BOM, so we still have quorum
(WebKit, Presto, Gecko) in favor of giving the BOM precedence.

> Should we switch back to the previous approach in the light of Trident?

No, we should not flip-flop on this. (I discussed the matter with Travis at
TPAC. I’m not sure if the details should be considered Member-confidential, so
I don’t write the details here.)

> Has anyone actually discussed Anne's
> proposal with the CSS and XML people?

CSS Level 3 gives the BOM precedence (implemented in WebKit, Presto and Gecko).
Test case: http://hsivonen.iki.fi/test/moz/bom/no-charset-attribute.html1251

For JS, Gecko experienced incompatibility with deployed content when not giving
the BOM the precedence in the case of JS, so I fixed Gecko to give the BOM the
precedence in the JS case.

Frankly, XML should just follow HTML, CSS and JS behavior for consistency. The
worst that can happen is that previously ill-formed docs become well-formed. If
someone has a problem with that, I suggest they fight the 5th edition first.

I think this bug should go back into the resolved state without spec changes.

You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 27 November 2012 08:22:04 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:34 UTC