[9530] in www-talk@info.cern.ch
Re: bug, or "feature"?
daemon@ATHENA.MIT.EDU (Dave Long)
Tue Jan 2 14:46:44 1996
To: Shel Kaphan <sjk@amazon.com>
Cc: www-talk@w3.org
In-Reply-To: Your message of "Fri, 29 Dec 1995 18:00:42 PST."
<199512300200.SAA27872@bert.amazon.com>
Date: Tue, 02 Jan 1996 11:27:07 -0800
From: Dave Long <dave@navisoft.com>
Resent-From: www-talk@w3.org
>I've just discovered that with some popular browsers, including the
>latest from Netscape, if you do a GET on a URL with a fragment (an
>anchor, a "#something" on the end), and the server issues a redirect
>(302) so that a different document is fetched, then the browser will
>NOT seek to the anchor to the ultimately viewed document -- you end up
>staring at the beginning of the page.
>
>Do people think this is
>a) a bug
>b) a feature
>c) none of the above ?
Ok, how about the reverse of this? You do a GET on an URL without
a fragment (an imagemap, say), and the server issues a 302 *with*
a fragment (to a glossary page, say). Should the browser:
a) seek to the fragment given in the redirect
b) start at top of page, since the original didn't start with a fragment
c) none of the above - discuss
-Dave
