[whatwg] Fw: Fw: Lists, <ins>/<del>, and <a>

Andrew Fedoniouk news at terrainformatica.com
Tue Aug 29 22:09:56 PDT 2006

> ----- Original Message ----- 
> From: "Alexey Feldgendler" <alexey at feldgendler.ru>
> To: <whatwg at whatwg.org>
> Sent: Tuesday, August 29, 2006 9:18 PM
> Subject: Re: [whatwg] Fw: Lists, <ins>/<del>, and <a>
>> On Wed, 30 Aug 2006 10:57:51 +0700, Andrew Fedoniouk 
>> <news at terrainformatica.com> wrote:
>>>>> Probably, lists should implement a special DOM interface which allows 
>>>>> to
>>>>> iterate over the list items. Tables have such an interface.
>>> Why not to implement just one simple function:
>>>   function foo(element) { ... }
>>>  ...
>>>  someListElement.select( "li", foo);
>>>  -or-
>>>  someListElement.select( "li:not(li li)", foo);
>>>   instead of multiplying that interfaces?
>> This is guessing. Right now, it took you two attempts to construct a 
>> selector which doesn't match too many or too little nodes. Note that 
>> rules may change in the future. For example, there has been a proposal to 
>> allow OL and UL as direct descendants of other OL or UL -- if this is 
>> accepted, you'll need to update your selectors once again, making them 
>> still more complex.

 Agreed in general, "I wish you to live in an era of changes" is pretty old
 Chinese damnation.
But it is at least not worse than difference in DOM interface
 implementations in different UAs.

 Less number of interfaces - stronger hope that they will be implemented

> On the other hand, the list can be required to "know" what its items are.

 I didn't get this one, sorry.

 Andrew Fedoniouk.

>> -- 
>> Alexey Feldgendler <alexey at feldgendler.ru>
>> [ICQ: 115226275] http://feldgendler.livejournal.com

More information about the whatwg mailing list