[wp-hackers] Strange errors with the link checker

[John Blackbourn]

I'd say that providing the user with the convenience of having the
page scroll down is better than your page being 100% W3C valid.

2009/9/5 Alan Castonguay <alan at verselogic.net>:
> Browsers seem to honor a name= fragments and whatever id= the same way. I
> don't think the w3 checker likes the latter. The fragment is only to scroll
> down the page to the comment box, and that behavior is not strictly
> required.
>
> Alan J Castonguay
>
> Sent from my iPhone
>
> On Sep 5, 2009, at 11:59 AM, Harish Narayanan <harish.mlists at gmail.com>
> wrote:
>
>> By default, WordPress generates something like the following URI to
>> reply to specific comments:
>>
>> http://foo.org/blog/post/?replytocom=123456#respond
>>
>> When I pass a page with comments through the W3C link checker, I see
>> errors like the following for each comment:
>>
>> Some of the links to this resource point to broken URI fragments (such
>> as index.html#fragment).
>>
>>
>> 1. Does anyone see why this happens? There is a <div id="respond"> on
>> the default page.
>> 2. Is the #respond part of the replytocom link necessary?
>>
>> Thanks,
>> Harish
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>