Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Comment 2 by jteh on 2008-05-30 02:45
The most efficient way to navigate quickly is to find a node (element) of a given type; e.g. quick navigation for form fields, links, etc. We could move to the next node which isn't a link, but in a navigation bar, this could well be a list item which contains a link. This is obviously not what is desired. This means that we must resort to scanning the text of the buffer, which is not simple due to the complex nature of most documents. Also note that searching for the next piece of text which isn't contained within a link is not always very accurate; e.g. navigation bars containing unlinked items or headings.
There are more efficient, accurate ways of quickly navigating a page. For example:
If anyone can come up with an algorithm (or even better, some code) to do this, we will definitely consider implementing it. However, at this stage, I don't believe this should block 0.6.