Phillips, Addison wrote:
I am writing on behalf of the I18N Core WG who discussed the
Selectors API WD in our call of 3 December [1].
We reviewed the Selectors API working draft. In reviewing this draft,
we did not find any internationalization issues in the text of the
document. However, we would like to point out that the CSS3 Selectors
themselves have outstanding internationalization comments not
addressed in the current version of that document [4] and which would
(we think) impact anyone who were to implement the Selectors API. Our
comments on CSS3 Selectors are located at [2]. We also note that
Unicode Normalization is not treated anywhere in this draft or in
CSS3 Selectors.
I'm not sure how I can address this issue. While I understand that the
CSSWG have not yet adequately addressed the i18n issues in their spec,
there's nothing I can do to resolve that.
Since this API defers all processing requirements for selectors to the
selectors spec (with the exception of trimming whitespace), it is the
responsibility of selectors to deal with Unicode normalisation issues.
I could not define any normalisation in this spec without indirectly
affecting how selectors work in other specs that use them, like CSS.
We are concerned that changes in CSS3 might impact implementation of
Selectors API and/or the text thereof and think our concerns probably
should be addressed before Selectors API advances to the next level
of maturity.
I do not believe the limitations of Selectors can have a direct impact
implementation of this API.
This is the last issue I need to address before asking to have this spec
proceed to CR, so I would like to be able to resolve it as quickly and
as easily as possible. If you have any proposals as to how exactly I
can address it, I will certainly try and do so.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
