- From: Paul Jones <paul@raygun.urbana.mcd.mot.com>
- Date: Fri, 17 May 1996 21:56:41 -0500 (CDT)
- To: CTaylor@wposmtp.nps.navy.mil (Charles Peyton Taylor)
- Cc: mudws@mail.olemiss.edu, www-html@w3.org
Charles Peyton Taylor said: > What I meant: > > ID would be very useful if it were implimented in > all browsers the way it is in UDI-WWW or (I think) > Arena. It is, however, not very backwards-compatible. > Like, not at all. Furthermore, and I think Dan Connelly > said something to this effect, if it were in the spec, > the real spec, people would think they could do things > like > > <h1 id="beginning"></h1> > > and then later > > <a href="beginning"></a> > At least one person (me) thought this. I use ID and CLASS in anchors to make references all over my document, to definitions, tables, headers, figures, whatever. CLASS tells how it is to be displayed at the reference site. So I might have: <H1><A ID=INTRO NAME=INTRO></A>Introduction</H1> . . . As mentioned in <A HREF="#INTRO" CLASS=HDRPAGE>The Introduction</A>, we recall that blah blah blah.... and this causes "Introduction on page 1-3" or some such to show up. The rendering tool knows to omit the anchor text in this case. If the document is referenced with a browser, the browser ignores all the attributes but displays a properly highlighted anchor. I can define all the classes of display I want in my FOSI for whatever will match the object to which I refer. It would probably be better to put the CLASS and ID in the H1 but it just worked out more easily this way for the time being in my implementation. PJ -- Paul Jones, Motorola MCG paul@urbana.mcd.mot.com 1101 E. University Ave. Voice: (217) 384-8529 Urbana, IL 61801, USA FAX: (217) 384-8550
Received on Friday, 17 May 1996 22:55:10 UTC