W3C home > Mailing lists > Public > spec-prod@w3.org > October to December 2001

Re: anchors in W3C specs

From: Martin Duerst <duerst@w3.org>
Date: Wed, 05 Dec 2001 13:41:16 +0900
Message-Id: <4.2.0.58.J.20011205134045.03aca780@localhost>
To: Paul Grosso <pgrosso@arbortext.com>, Susan Lesch <lesch@w3.org>, spec-prod@w3.org
I agree with Paul that the XHTML compatibility guidelines
are a good idea to maintain for our specs.

Regards,

At 11:27 01/12/04 -0600, Paul Grosso wrote:
>What is the accepted way of doing links in the published
>HTML for W3C specs?
>
>Specifically, I'm concerned with the use link targets such
>as <div id="foo"> that are expected to be the target of a
>link such as <a href="#foo">.  While this is allowable in
>XHTML, this is not compatible with HTML and does not follow
>the XHTML guidelines for compatibility with HTML browsers;
>such links do not work, for example, in Netscape 4.x browsers.
>
>I have noted an increasing number of such links in W3C
>documents, and I note with great concern that the W3C link
>validator does not even so much as give a warning for such
>links which are effectively BROKEN for all Netscape users.
>
>Personally, I'd like to see our pub styles indicate that
>W3C specs should follow the XHTML compatibility guideline
>that suggests targets of the form <a id="foo" name="foo">
>are used, and I'd like to see the link validator give
>errors (or at least warnings) for link targets using an
>id since that won't work in many of the deployed browsers.
>
>paul
Received on Wednesday, 5 December 2001 01:57:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:19:11 GMT