Re: [whatwg] getElementsByClassName()

2006-02-04 Thread Lachlan Hunt
James Graham wrote: Also I would be surprised if there weren't multiple implementations of getElementsByClassname floating around in javascript libraries. So you can't really call it unimplemented. While there are many JavaScript implementations (I even wrote one myself a few months ago), all

Re: [whatwg] getElementsByClassName()

2006-02-04 Thread James Graham
Jim Ley wrote: On 2/4/06, Brad Fults <[EMAIL PROTECTED]> wrote: The reasons why XBL is not currently an acceptable substitute are numerous, including its extremely limited implementation, So something with no implementation should be taken over something with an existing implementation, that's

Re: [whatwg] getElementsByClassName()

2006-02-04 Thread Jim Ley
On 2/4/06, Lachlan Hunt <[EMAIL PROTECTED]> wrote: > One issue with a Selector method though, how do we handle namespace > prefixes? Selectors states that the mechanism for declaring a namespace > prefix is left up to the language implementing Selectors. If we say the > script uses the same pref

Re: [whatwg] getElementsByClassName()

2006-02-04 Thread Lachlan Hunt
Jim Ley wrote: ...neither is it apparent that a classname specific shortname is worthwhile when a CSSSelector one would be more appropriate. It should be called getElementsBySelector, rather than CSSSelector, because selectors is not specific to CSS (it's not even called "CSS Selectors" any m

Re: [whatwg] getElementsByClassName()

2006-02-04 Thread Jim Ley
On 2/4/06, Brad Fults <[EMAIL PROTECTED]> wrote: > I fully admit the possibility that this may be better accomplished > with some other theoretical and/or vendor-specific technology, but you > again missed the core point. the core point is we're inventing something new to meet a use case, you inve

Re: [whatwg] getElementsByClassName()

2006-02-04 Thread Brad Fults
On 2/4/06, Jim Ley <[EMAIL PROTECTED]> wrote: > On 2/4/06, Brad Fults <[EMAIL PROTECTED]> wrote: > > I can't believe that you're so insistent upon this extremely narrow > > set of use cases and that there aren't any other popular use cases for > > getElementsByClassName(). > > It's the only one tha

Re: [whatwg] getElementsByClassName()

2006-02-04 Thread Michel Fortin
Le 2006-02-03 à 19:20, Simon Pieters a écrit : I have a some markup like this: Tab 1 Tab 2 ... ... With the help of a style sheet, the script transforms this into some sort of tab view. It search for each div of class "pane". I

Re: [whatwg] getElementsByClassName()

2006-02-04 Thread Jim Ley
On 2/4/06, Lachlan Hunt <[EMAIL PROTECTED]> wrote: > Jim Ley wrote: > For example, if an author > marked up dates in their document like this (due to the lack of a date > element) > > 2006-02-03T01:30Z A nice use case, and one well met by XBL including the currently implemented -moz-binding, met m

Re: [whatwg] getElementsByClassName()

2006-02-04 Thread Jim Ley
On 2/4/06, Brad Fults <[EMAIL PROTECTED]> wrote: > I can't believe that you're so insistent upon this extremely narrow > set of use cases and that there aren't any other popular use cases for > getElementsByClassName(). It's the only one that's ever been voiced without the extreme prompting now ge

Re: [whatwg] getElementsByClassName()

2006-02-04 Thread ROBO Design
On Sat, 04 Feb 2006 03:49:23 +0200, Brad Fults <[EMAIL PROTECTED]> wrote: On 2/3/06, Jim Ley <[EMAIL PROTECTED]> wrote: <...> I can't believe that you're so insistent upon this extremely narrow set of use cases and that there aren't any other popular use cases for getElementsByClassName(). I

Re: [whatwg] Update to the Adoption Agency Algorithm

2006-02-04 Thread Bjoern Hoehrmann
* Ian Hickson wrote: >> Well, if you approach the problem by asking whether it's possible that >> things become non-compliant, you'll either have to analyze any and all >> dependencies like server-side scripts and workflows or you'd generate >> false negatives, since adding some external data to