Forum Moderators: open
for example <H2><A HREF="chapter2.htm" NAME="chapter2">chapter 2 </A></H2>
Basically I have this:
(page 1)
<html>
<a href=http://www.someurl.com#test4>Click here to see bla bla bla on the next page</a>
</html>
(page 2)
<html>
<a name=test4>bla bla bla</a>
</html>
The fragment identifier is a string after URI, after the hash, which identifies something specific as a function of the document. For example in the object
[widget...]
the string "frag" is the fragment identifier. It is badly named, as it can identify anything.
To ensure that this internal linking works properly, add the fragment identifiers to the file for each location you wish to jump to.
Example as given before
<H2><A HREF="location">Location</a></H2>
Because the text already is contained in an anchor element, use the Name= attribute to name the fragment.
<H2><A HREF="location" NAME="location">Location</a></H2>
You can find out more information on fragment identifiers here
[w3.org...]
[edited by: webmasterguy at 5:12 pm (utc) on Oct. 19, 2004]
<a name="test4">bla bla bla</a>
I have this issue myself on a pretty extensive calendar page. My solution was to break the one big table into several other tables (month by month, not season by season or year by year) so I could place the named anchors at the top of a "dedicated" table instead of within it.
A least that is the only behavior I ever could get. But there is an advantage here - breaking up one long table into many tables that follow each otherdown the page has the advantage of rendering some content in the visible window, faster.
