* 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 the
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().
If
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
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)
span class=date2006-02-03T01:30Z/date
A nice use case, and one well met by XBL including the currently
implemented
Le 2006-02-03 à 19:20, Simon Pieters a écrit :
I have a some markup like this:
ul
lia href=#tab1Tab 1/a/li
lia href=#tab2Tab 2/a/li
/ul
div id=tab1 class=pane
...
/div
div id=tab2 class=pane
...
/div
With the help of a style sheet, the
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
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),
