|
|
Posted by Andy Dingley on 02/06/07 15:18
On 6 Feb, 12:32, "Gary" <garyuse...@myway.com> wrote:
> Im just experimenting with internal linking.
Don't use it if it's only a substitute for having pages short enough
to comprehend without massive scrolling. Separate pages (still with
nav links to them) generally make a better site than one huge "roll o'
wallpaper"
As an example, here's a guy who designs great gas burners, but bad web
pages
http://www.abana.org/ronreil/design1.shtml
(I do bronze casting and forging with a couple of them)
> The problem I have is that the page doesnt jump to the link, but only
> the page the link is on.
That's all it's expected to do. Exactly how a particular browser
behaves is up to that browser's implementors and could be almost
anything. Generally the link target will be scrolled until it's
visible in the window, but they don't guarantee placing it right under
the mouse cursor. Most of them try to minimise scrolling, so the
effects vary depending on how long the page is and which direction you
approached it from.
> Here is my HTML: -
That looks broadly OK, although repeated <br> is bad coding style and
<br /> is wrong for HTML (it's XHTML, so either don't use it or search
the ng. archives for why not to). You have the usual common error
correct, in that you've used the "#" correctly.
We don't generally like posted HTML fragments, preferring URLs to live
sites. Sometimes there are typos or server config problems that aren't
visible otherwise.
The other poster's idea of substituting name attribute instead of id
and in adding an explict <a name="..." > is obsolete coding style and
wouldn't help anyway. I'd advise against doing it this way, although
it isn't strictly wrong to do so.
Navigation:
[Reply to this message]
|