key navigation and visible area of the page

[Arend van Beelen jr.]

On Monday 17 May 2004 17:19, Lubos Lunak wrote:
> On Monday 17 of May 2004 11:52, Tobias Anton wrote:
> > On Mittwoch, 12. Mai 2004 09:49, Lubos Lunak wrote:
[snip]
> > The amount of scrolling is limited to at most one page so that tab can be
> > used to view the entire page following the focus order that the author
> > intended. It is particularly useful for people that don't use a mouse and
> > I don't see a necessity to break the known behaviour for them. If you
> > found any bugs in conjunction with type-ahead find or the selection code,
> > please report or fix them instead of cutting out working code.
>
>  I already described the problem. The Tab behaviour is weird if the focused
> item is not visible. Go e.g. to
> http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kdelibs/khtml/khtmlview.cpp , hit
> Tab few times, scroll ten pages down, and start hitting Tab again. I doubt
> you can guess what it will do, but even if you do, I don't consider that to
> be known behaviour, in fact I was pretty confused when that happened to me.
>
>  But perhaps this problem would go away after changing Tab to start from
> the visible area, like Arend suggested. What's your opinion on this?
I tend to agree with Lubos here. But I don't think when Tab starts in the 
visible area, this will still be a real problem, because you rarely have to 
jump (a lot).
However, I'm not really sure about where to start in the visible area when, 
like Tobias mentioned, the author has set its own Tab order. Should we:
- ignore the visible area
- find the object with the next logical order but still in the visible area
- or just ignore the Tab order

Personally I would prefer the second option. Thoughts?

[snip]

-- 
Arend van Beelen jr.
http://www.liacs.nl/~dvbeelen

So if you want my address, it's number one at the end of the bar.
-- Marillion