STEPS TO REPRODUCE
1. Open http://www.w3.org/TR/REC-CSS1
2. Hit tab until you have focussed the "Terminology" link.
3. Hit enter (to follow the internal link to the "Terminology" section).
4. Hit tab to highlight the "" link under "child element".
After you hit the tab in step 4, you are moved all the way back up to the
contents list. This is very disturbing.
I propose that the current tabbing position be moved to the target anchor
whenever the page is scrolled by following an internal link.
This bug was filed based on a comment in firstname.lastname@example.org, part of which is
On Fri, 5 Oct 2001, Charles McCathieNevile wrote:
> The user scenario is as follows:
> Open a page which contains some internal links.
> Use the keyboard (tab key for these browsers) to get to an internal link.
> Use the keyboard to follow the link to another art of the document.
> The "tab order" remains where it was, so the user tabs next to whatever was
> the link after the one followed, not the link after the anchor that they
> (think that they) moved to.
> The HTML 4.01 specification appears to support this behaviour or the more
> natural one (as demonstrated for example by Lynx) of placing the user in the
> tabbing order starting at the point to which they have navigated.
keybd bav. bryner's?
Hmm... I couldn't get a link bar from the test case page, even on a recent build.
Anyway, this is a tab navigation bug. -> bryner
Should this apply whenever I follow a link with a named anchor component, or
only when the link and target are part of the same document?
document to the bottom after adding text to the bottom of the page? Should
that move focus to the bottom of the page, or leave it where it is? (My code
on http://www.cs.hmc.edu/~jruderma/js/calc/ immediately focuses a textbox after
scrolling to the bottom, so it wouldn't really matter for my page.)
Will Mozilla make the focus on the named anchor visible? This could be tricky,
because many named anchors are empty, and some are never closed and "enclose"
paragraphs as a result.
There is similar to bug 66597
(Tab should start from insertion point or beginning of select).
For example, after a find, make tab navigation relative to the last found text.
It would make sense to fix that bug first, then fix this bug by setting the
caret to the beginning of named anchor.
I have a fix for this now in bug 66597
nsbeta1+ per ADT triage team
How can this be plused when the bug it depends on was minused?
testing this using a build from aaronl [2/8] on win2k, i crash when going thru
the original recipe at step 3 --right after hitting the Enter key when the
"Terminology" link is in focus. [side note: have got caret browsing off.]
testing using a 2/18 test build from aaronl [win2k, mozilla].
* i no longer crash at step (3), yay!
* however, at step (4) when i hit tab to go to "" under "child element", i'm
brought to the "1 Basic concepts" link instead. :(
so, this still doesn't look fixed...
using an even newer test build [thx aaronl], this looks fixed.
...and still looks good w/a test build from 2/20.
works with the 2/23 test build [exciting comment, no?].
fix checked in
Shweeet! Thanks guys.
hey hixie, i cannot remember which platforms you have access to presently. but
for grins i vrfy'd this on linux rh7.2, mac 10.1.3 and win2k. yeah!