lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

lynx-dev History page handling suggestions


From: Jacob Poon
Subject: lynx-dev History page handling suggestions
Date: Thu, 23 Apr 1998 13:09:19 -0400

Bug
===

1. If there is only 1 link in the history page (namely, link number 0),
following it from HP will push the link into the history stack, which
shouldn't. 

Suggestions
===========

1. When following any non-topmost link in HP, Lynx shouldn't push it into
the stack.  Instead, only current stack level is altered.

2. PREV_DOC command should not pop history stack.  It should only lower
current stack level.

3. History stack should be popped only when you are not on the top of the
stack, and follow a URL that is different from the one directly above
current stack level.

4. With PREV_DOC command, it will be very helpful to have a NEXT_DOC
command which goes to the next document (next higher level URL in history
stack).  If you are already at the topmost stack level, it works the same
as ACTIVATE command.

I am asking for all these features (especially suggestion number 4) not
just because my previous exposures to certain graphical browsers (ok, it
_is_ mostly because of certain graphical browsers :).  I am asking for
them primarily because it is very helpful on viewing a long document, say
10+ pages.  Without NEXT_DOC, when you are at the middle of the long
document, then go back to previous document and came back to browse it
again, you will always resume at the beginning of the long document, which
can be quite a hassle.  With NEXT_DOC, you can go back and forth between
large files in the history stack and resume viewing at any point of the
stacked URLs, even the ones that are no longer in the cache.  BTW, to make
#4 work, it will requires suggestions #2 and #3 to be implemented.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]