W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2006

[whatwg] Update to the Adoption Agency Algorithm

From: Blanchard, Todd <tobl@amazon.com>
Date: Fri, 3 Feb 2006 09:10:20 -0800
Message-ID: <B13FD3F68424FA4DAD378D12312011D8011E64BA@exchg-sea5-04.ant.amazon.com>
>Any markup that causes a browser to automatically clone a node will be non-conformant and 
>will be flagged as erroneous by a validator.

You are assuming that validators run javascript - they generally don't. (I'm hoping to add it to Scrutinizer http://www.blackbagops.net/seaside/html ) but that would make it unique in the world of validators.

Browser makers can't just punt on this issue - you have to help the developers more.  As it is now we spend way too much time writing little probe programs to reverse engineer browser behavior to figure out why our nifty AJAX apps don't work.  


-----Original Message-----
From: whatwg-bounces@lists.whatwg.org [mailto:whatwg-bounces@lists.whatwg.org] On Behalf Of Lachlan Hunt
Sent: Friday, February 03, 2006 3:21 AM
To: Gervase Markham
Cc: whatwg
Subject: Re: [whatwg] Update to the Adoption Agency Algorithm

Gervase Markham wrote:
> Lachlan Hunt wrote:
>> Errors caused by the result of duplicate IDs either in the markup or 
>> indirectly as a result of badly nested elements can be fixed by a 
>> quick visit to the validator (or other conformance tool) or by making 
>> use of any or all of those tools I mentioned above.
> 
> It's much harder to spot them when they are dynamically generated by 
> e.g. a cloneNode operation. You can't submit your browser's DOM tree 
> to the validator...

Any markup that causes a browser to automatically clone a node will be non-conformant and will be flagged as erroneous by a validator.  Of course it won't say duplicate ID, but it will give errors about badly nested elements.

--
Lachlan Hunt
http://lachy.id.au/
Received on Friday, 3 February 2006 09:10:20 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:26 UTC