[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LYNX-DEV lynx bug with NAME value in anchors 2.7.1
From: |
David Woolley |
Subject: |
Re: LYNX-DEV lynx bug with NAME value in anchors 2.7.1 |
Date: |
Wed, 26 Nov 1997 23:57:51 +0000 (GMT) |
> Error occurs on HTML code included below.
NO! The error occurs IN the HTML code. Lynx is implementing UNDEFINED
in a perfectly reasonable way.
E.g. quoting from HTML 4.0 (draft 8 July 1997):
The A element
....
name = cdata
This attribute indicates that the element is being used to define
an anchor. The value of this attribute is a unique anchor name. The
^^^^^^
scope of this name is the current document. Note that this attribute
shares the same name space as the id attribute.
(My ^^^^^)
>
> Error is that "init.c" link leads to "Makefile" file if NAME values
> ("tex2html1") in the two achors are exactly the same, as below. If one
> of the values is changed, the "init.c" link leads to "init.c".
>
> <A NAME="tex2html1"
> HREF="lab1/Makefile">Makefile</A>
> and
> <A NAME="tex2html1"
> HREF="lab1/init.c">init.c</A>
> to your newly-created directory.