W3C home > Mailing lists > Public > www-html@w3.org > July 1998

Re: Ah! Another HTML query!

From: nir dagan <dagan@upf.es>
Date: Wed Jul 22 07:07:02 1998
Message-Id: <199807221059.MAA01041@sahara.upf.es>
To: gwalla@hotmail.com
Cc: www-html@w3.org
My comment is below.

> >In one of my pages, I have a listed about 10 topics, one
> >after the other, all hyperlinked (to a detailed paragraph
> >later in the page) through <A HREF=#TOPICx"> and correctly
> ><A NAME>d. The problem is, when the page opens up, the 10
> >links all assume the VLINK color I've given, even before I
> >click on them.
> I've noticed this too. Unfortunately, this is one of those 
> implementation-dependent problems. Some UAs use the VLINK color to mean 
> that the page has been visited, not the specific part. This makes a 
> certain amount of practical sense (the browser can't be certain that you 
> haven't been to a certain part of a document if you didn't link there 
> directly).
> If I remember correctly, MSIE has this problem, while NN only uses the 
> VLINK color if the exact part has been linked to before.

Its a problem if you are used to Netscape. I think that Explorer's 
(and Opera's) implementation is much better. 
The basic navigation unit is the page.

If you go to the named anchor by scrolling down the page, Netscape still 
will show it as unvisited. Users then get confused and think later they 
did not visit the segment.  Clearly Netscape's implementation is 
incosistent. If user's history has to do with "anchors read", they have 
to change the link's color to visited even if you get there by scrolling.

In MSIE and Opera, user's history has to do with "pages visited" 
not with "anchors read". Their implementaion is consistent and 
not confusing.

Nir Dagan
Received on Wednesday, 22 July 1998 07:07:02 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:48 UTC