Lachlan Hunt wrote:
Jonas Sicking wrote:
Anne van Kesteren wrote:
On Fri, 15 Feb 2008 19:36:21 +0100, Jonas Sicking <[EMAIL PROTECTED]>
wrote:
Lachlan Hunt wrote:
I have added the following text to the spec:
"If the user agent also supports some level of CSS, the
implementation
must support the same set of selectors that are supported by the
CSS
implementation."
...
The text above only says that the API impl has to support the same set
as the CSS impl. It doesn't say that the CSS impl has to support the
same set as the API impl. I.e. I see nothing that prohibits the API
impl from supporting additional selectors.
I have clarified the text to remove any possible ambiguity related to
this issue. The spec now states:
"If the user agent also supports some level of CSS, the implementation
must support the same set of selectors in both these APIs and CSS."
Thanks, that makes it much more clear.
I do sort of think that it's a pity to disallow a selectors
implementation in a browser from implementing additional selectors on
top of the ones in the CSS implementation, for example for the reasons
Boris mentioned. I don't feel very strongly about it, but I'm wondering
what the rationale for forbidding it is.
/ Jonas
