W3C home > Mailing lists > Public > spec-prod@w3.org > July to September 2001

Re: Anchor semantic lost...

From: Charles McCathieNevile <charles@w3.org>
Date: Mon, 9 Jul 2001 10:38:00 -0400 (EDT)
To: Norman Walsh <Norman.Walsh@Sun.COM>
cc: <spec-prod@w3.org>
Message-ID: <Pine.LNX.4.30.0107091037130.14106-100000@tux.w3.org>
    <h2><a name="intro" id="intro"></a>1. Introduction </h2>
    <p>This specification...

works everywhere so far as I can tell...

Charles McCN

On 9 Jul 2001, Norman Walsh wrote:

  / Karl Dubost <karl@w3.org> was heard to say:
  | The spec-prod tools have a very bad side effect on anchors
  | semantic. It would be great to fix it.
  | See my report in http://www.w3.org/2001/07/QA-revxmlinfoset.html#toc
  | Anchors and section.

  While I appreciate the intent, translating this

    <a name="intro"/><div>
    <h2>1. Introduction </h2>
    <p>This specification...

  into this:

    <h2 id="intro">1. Introduction </h2>
    <p>This specification...

  fails because there are many browsers that don't recognize that #intro
  should go to the element with ID intro; they insist on locating an A
  with a NAME of intro.

  And translating into this:

    <h2><a name="intro">1. Introduction </a></h2>
    <p>This specification...

  fails because some browsers make the text surrounded by an <A name="">
  tag blue and underlined. (They shouldn't, but they do.)

                                          Be seeing you,

Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1 617 258 5999
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)
Received on Monday, 9 July 2001 10:38:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:42:16 UTC