key navigation and visible area of the page

[Tobias Anton]

On Montag, 17. Mai 2004 21:32, Arend van Beelen jr. wrote:
> 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?

It can be confusing if the element receiving focused depends on the previous 
cursor position, even though the last user action was not related to cursor 
movement.

That's why I think we should ignore the tab order in case of d->scrollBarMoved 
and pick the most upper left completely visible element. If there is no such 
element, we'd fall back to the old tabbing behaviour, respecting the tab 
order in that case.

Tobias