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 the tabbing order (regardless of whether it is on the screen), scroll to make it visible, and leave this state. - The scroll-up, scroll-down, move-page-up, and move-page-down actions would scroll the document but never give focus to a link. - The move-cursor-left, move-cursor-down, move-cursor-up, and move-cursor-right actions would exit this state. - How about the search-typeahead, search, and search-back actions? Is that what you are asking for? How important is the change to you, given the two workarounds of (a) setting document.browse.links.use_tabindex = 0 and (b) pressing Home after the document has loaded? > Adding features based on donations is a standard Open Source > practice, and I have been doing it for many projects now. For legal (31.3.2006/255) as well as personal reasons, I don't want to get involved in any ELinks-related monetary donations. _______________________________________________ elinks-users mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-users
