W3C home > Mailing lists > Public > www-style@w3.org > February 2009

RE: [selectors-api] Selectors API I18N Review...

From: Richard Ishida <ishida@w3.org>
Date: Wed, 4 Feb 2009 15:03:32 -0000
To: "'Anne van Kesteren'" <annevk@opera.com>, "'Henri Sivonen'" <hsivonen@iki.fi>
Cc: <public-i18n-core@w3.org>, <www-style@w3.org>
Message-ID: <00a201c986d9$bf9ecb50$3edc61f0$@org>

Hi Anne,

No, this is a theoretical outcome if some browsers did start normalizing.  I don't know of any that do at the moment - though I haven't exactly scoured the whole list of UAs at this point.

RI

============
Richard Ishida
Internationalization Lead
W3C (World Wide Web Consortium)

http://www.w3.org/International/
http://rishida.net/



> -----Original Message-----
> From: Anne van Kesteren [mailto:annevk@opera.com]
> Sent: 04 February 2009 14:59
> To: Richard Ishida; 'Henri Sivonen'
> Cc: public-i18n-core@w3.org; www-style@w3.org
> Subject: Re: [selectors-api] Selectors API I18N Review...
> 
> On Wed, 04 Feb 2009 15:54:36 +0100, Richard Ishida <ishida@w3.org> wrote:
> > If some current browsers do support normalization and others don't, we
> > could occasionally have an issue for those who don't
> > realise that the browser(s) they tested on hid a normalization operation
> > that others at that time don't.
> 
> Is this theoretical or is there actually such a browser? If there is, does
> it normalize during parsing or while comparing? Are the specifics
> documented somewhere?
> 
> 
> --
> Anne van Kesteren
> <http://annevankesteren.nl/>
> <http://www.opera.com/>
Received on Wednesday, 4 February 2009 15:03:31 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:16 GMT