Re: [selectors-api] Consider backporting find() behavior to querySelector()

2012-06-20 Thread Marat Tanalin | tanalin . com
20.06.2012, 18:14, "Lachlan Hunt" : > 4. Support for returning elements that are not descendants of the > context object. > > This feature allows a selector to be constructed such that it matches an > element anywhere in the tree relative to the context element. This > feature is not relevant t

Re: [selectors-api] Consider backporting find() behavior to querySelector()

2012-06-20 Thread Marat Tanalin | tanalin . com
20.06.2012, 18:26, "Lachlan Hunt" : > In particular, is there really value in adding two distinct methods that > differ only by whether they return 1 element or a collection?  Resolving > this issue first would help with resolving the naming issue. > > It should be noted that JQuery/sizzle does not

Re: [selectors-api] Consider backporting find() behavior to querySelector()

2012-06-19 Thread Marat Tanalin | tanalin . com
20.06.2012, 00:38, "Tab Atkins Jr." : > On Mon, Jun 18, 2012 at 10:59 PM, Simon Pieters wrote: > >>  On Mon, 18 Jun 2012 16:57:17 +0200, Kang-Hao (Kenny) Lu >>   wrote: >>  We have lots of shipped APIs with worse names. I think we should live with >>  past mistakes, try not to make them again, and

Re: [webcomponents] Custom Elements Spec

2012-05-04 Thread Marat Tanalin | tanalin . com
> So what happens in browsers that don't support components? Or in search > engines or other data analysis tools that are trying to extract the > semantics from the page? Elements with custom tag-names would have EXACTLY SAME semantic (as for core HTML5 semantics) meaning as a common container (S

Re: [webcomponents] Custom Elements Spec

2012-05-04 Thread Marat Tanalin | tanalin . com
Ian, it seems you are continuing to confuse two very different things: 1. local semantics; 2. extending existing elements. They have completely different purposes. Web-developers generally do not need to _extend_ existing elements (purpose of such extending itself is quite mysterious for me).

Re: Custom Tags and Local Semantics

2012-04-23 Thread Marat Tanalin | tanalin . com
FWIW: my proposal (already successfully rejected) for custom elements (real custom elements with really arbitrary tag names allowed) in W3 bug tracker from 2011-09-03: https://www.w3.org/Bugs/Public/show_bug.cgi?id=14011 BTW, it seems local semantics (what my proposal is about and what you are

querySelectorAll() -- selecting _immediate_ children of element

2012-01-09 Thread Marat Tanalin | tanalin . com
querySelector() and querySelectorAll() methods are exciting features, but they do not allow select _immediate_ children of reference element. To address this lack, we could use following syntax: var divs = refElement.querySelectorAll('> DIV'); Here 'divs' variable contains list of DIV eleme