GNOME Bugzilla – Bug 607326
“back” button for hyperlinks
Last modified: 2013-02-18 09:39:52 UTC
Hello! Short version: Please add a one-click method to return the viewer to the last page / scroll position it had before the last intra-document hyperlink was clicked. Evince currently supports intra-document hyperlinks, at least in PDF documents. These are often used in all sorts of books and articles to link to foot-notes, references and the like. Clicking on such a link causes Evince to scroll to a different (usually) part of the document. This works similar to how web browsers handle hyperlinks, which is very nice. However, unlike browsers, Evince doesn't seem to have a “back” button. This leads to an inconvenient situation: it's very easy to see what a hyperlink leads to, but quite hard to go back to what one was reading before clicking the link. One can try to remember the current page, and type it back in the “select page” box on the tool-bar, but this is very asymmetric with respect to the input effort needed. (Also, I at least almost always forget to check the current page.) It is especially annoying in long documents, like books, with links at the end. Actually, it's annoying enough that I found myself often skipping interesting links because of the sheer bother of going back to where I was. It would be nice to add a way to go back after clicking a hyperlink. A “Back” button on the tool-bar would probably do the job. It should probably be displayed only when the currently opened document type supports hyperlinks (even better would be only when the document has hyperlinks, if that's easy to determine), and active only after a hyperlink was clicked.
it would be really usefull with books index, when you are searching something, and you read index, some page in the middle of the book, again index, again some pages somewhere in the book..
*** Bug 639986 has been marked as a duplicate of this bug. ***
Seems a duplicate of Bug 169903 . BTW, there is now already a back button, but it's hard to find.
Indeed, it is duplicated and it was fixed yesterday. *** This bug has been marked as a duplicate of bug 169903 ***