W3C home > Mailing lists > Public > public-webapi@w3.org > February 2008

Re: [selectors-api]

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 19 Feb 2008 10:16:35 +0100
To: "Ian Hickson" <ian@hixie.ch>
Cc: "Boris Zbarsky" <bzbarsky@mit.edu>, "Lachlan Hunt" <lachlan.hunt@lachy.id.au>, public-webapi@w3.org
Message-ID: <op.t6rldxxi64w2qv@annevk-t60.oslo.opera.com>

On Tue, 19 Feb 2008 10:07:19 +0100, Ian Hickson <ian@hixie.ch> wrote:
> On Tue, 19 Feb 2008, Anne van Kesteren wrote:
>> >
>> > My suggestion was to allow the implementation to throw as soon as it
>> > detects any sort of misbehavior from the NSResolver.  Anne didn't like
>> > it.  Given that the implementation isn't allowed to do this, what _is_
>> > it allowed to do to comply with the "deal with broken or malicious
>> > NSResolvers" text?
>>
>> I think it has to go like this:
>>
>>   1. Get default namespace / resolve namespace prefixes
>>   2. Run the group of selectors over the "current" DOM
>>
>> And I like to believe that this is what the specification requires. But
>> maybe we should make it explicit in the method section that step 1 has
>> to happen first and that user agents are not allowed to do both at the
>> same time.
>
> So even prefixes that are never going to match in the current document
> have to be checked?

Well, the intent was more that prefixes are resolved before checking the  
DOM at all. If the UA doesn't think it needs to check prefixes that's fine  
(though it would probably still have to check the default namespace).


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Tuesday, 19 February 2008 09:12:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 February 2008 09:12:56 GMT