Yes. I got it. So the culprit actually wasn't elinks, but rather the forum, which had explicit instructions for a browser to focus on the form. The current behaviour is good enough for me.
Thanks. On Sun, Aug 12, 2007 at 12:45:02AM +0300, Kalle Olavi Niemitalo wrote: > Ligesh <[EMAIL PROTECTED]> writes: > > > Yeah, that worked. But what exactly is a tabindex? > > http://www.w3.org/TR/html401/interact/forms.html#adef-tabindex > > > And is there some way I can configure it properly? > > If I understand correctly, your complaint is that ELinks > automatically gives focus to the first link in the tabbing order, > and scrolls to make it visible. Whereas e.g. Iceweasel initially > gives focus to the entire document, and moving focus to the first > link in the tabbing order requires pressing Tab once. I suppose > that would map to the Down key (move-link-next action) in ELinks. > So, upon loading a document, ELinks should enter a state where: > - The move-link-next action would give focus to the first link in > the tabbing order (regardless of whether it is on the screen), > scroll to make it visible, and exit this state. > - The move-link-prev action would give focus to the last link in _______________________________________________ elinks-users mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-users
