On Thu, 24 Nov 2011 20:39:16 +0100, Yehuda Katz wyc...@gmail.com wrote:
Awesome. I wonder if there's any utility to linking to the exact thread
where the merge was agreed to?
I do not think so, but if people end up asking that a lot I will make sure
to do that.
Cheers,
--
Anne van
On Thu, Nov 24, 2011 at 5:19 PM, Julian Reschke julian.resc...@gmx.de wrote:
Well, the use case is to allow browsers to move to XPath2/XSLT2 at some
point in the future, without having to maintain another engine.
Sorry about bringing up the XPath2 rathole that's now expanding into
the XSLT2
On 2011-11-24 14:49, Robin Berjon wrote:
So, now for the money question: should we charter this?
Only if someone is volunteering to be the editor and drafts a spec.
--
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
On 2011-11-25 03:58, Tab Atkins Jr. wrote:
Alternately, assume that :matches() is eventually changed to allow
complex selectors. Using :scope there is completely fine.
I'm not sure what you mean. The current spec for matchesSelector does
allow complex selectors as it's defined to accept a
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14666
Anne ann...@opera.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
On Nov 25, 2011, at 10:03 , Lachlan Hunt wrote:
On 2011-11-24 14:49, Robin Berjon wrote:
So, now for the money question: should we charter this?
Only if someone is volunteering to be the editor and drafts a spec.
If no one else steps up to it I can, but I was under the impression that our
* Robin Berjon wrote:
If no one else steps up to it I can, but I was under the impression that
our good friends from Opera had a solution they could contribute — I
would hope in the shape of an editor :)
I started it some years ago, but then figured if anybody brought it up
the selectors shirts
On 2011-11-25 00:19, Sean Hogan wrote:
This has been raised before, but I'll restate it here.
How should the selector be expanded in
elt.findAll(div span, div :scope span)?
The implication of :scope has to be done on a per complex selector
basis, rather than applied to the entire list. That
On 26/11/11 12:00 AM, Lachlan Hunt wrote:
On 2011-11-25 00:19, Sean Hogan wrote:
This has been raised before, but I'll restate it here.
How should the selector be expanded in
elt.findAll(div span, div :scope span)?
The implication of :scope has to be done on a per complex selector
basis,
On 25/11/11 6:49 PM, Lachlan Hunt wrote:
On 2011-11-25 01:07, Sean Hogan wrote:
On 24/11/11 7:46 PM, Lachlan Hunt wrote:
On 2011-11-23 23:38, Sean Hogan wrote:
- If you want to use selectors with :scope implied at the start of
each
selector in the selector list (as most js libs currently do)
All -
I'm going to throw my 2 cents in here and say that, whatever ends up happening
with scoping, that the equivalent of the current
querySelector()/querySelectorAll() should be named matchesSelector().
As a longtime Web developer (and trainer of other Web developers) it is
important to me
On 25/11/11 5:53 AM, Yehuda Katz wrote:
So, the rules end up being very simple. find always evaluates against
the whole document. If one of the selectors starts with a combinator
or doesn't contain a :scope pseudoclass somewhere in it, :scope is
prepended to it. That's it.
12 matches
Mail list logo
