W3C home > Mailing lists > Public > public-html@w3.org > July 2009

Re: Non-character NCRs treated differently from literal non-characters

From: Ian Hickson <ian@hixie.ch>
Date: Sun, 26 Jul 2009 09:25:34 +0000 (UTC)
To: Henri Sivonen <hsivonen@iki.fi>
Cc: "public-html@w3.org WG" <public-html@w3.org>
Message-ID: <Pine.LNX.4.62.0907260924360.23663@hixie.dreamhostps.com>
On Thu, 9 Jul 2009, Henri Sivonen wrote:
> On Jul 8, 2009, at 04:04, Ian Hickson wrote:
> > On Wed, 10 Jun 2009, Henri Sivonen wrote:
> > > > > 
> > > > > But why, then, do non-character NCRs turn into REPLACEMENT 
> > > > > CHARACTER?
> > > > 
> > > > For consistency.
> > > 
> > > In that case, I suggest letting non-characters end up in the DOM in 
> > > both cases as is traditional.
> > 
> > Fixed.
> 
> Thanks.
> 
> For the C1 range, I see that you sided with IE and WebKit rather than 
> Gecko and Opera. Was that intentional?

Yes.


> The edit introduced one outright spec bug: Numbers above 0x10FFFF should 
> still turn into U+FFFD.

Fixed.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Sunday, 26 July 2009 09:26:10 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:48 UTC