[wp-hackers] Strange errors with the link checker
sojweb at indiana.edu
Sat Sep 5 20:47:00 UTC 2009
That's a valid use. See:
It is supposed to be case-sensitive... maybe there's mismatch in case
between fragment identifier and ID that the browser ignores, but the
validator catches? Or maybe the validator itself has a bug. Either
way, it's valid.
On Sep 5, 2009, at 4:30 PM, John Blackbourn wrote:
> 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
>> Alan J Castonguay
>> Sent from my iPhone
>> On Sep 5, 2009, at 11:59 AM, Harish Narayanan <harish.mlists at gmail.com
>>> By default, WordPress generates something like the following URI to
>>> reply to specific comments:
>>> 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
>>> as index.html#fragment).
>>> 1. Does anyone see why this happens? There is a <div id="respond">
>>> the default page.
>>> 2. Is the #respond part of the replytocom link necessary?
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers