GNOME Bugzilla – Bug 578837
unintuitive back and forward
Last modified: 2012-11-25 09:56:00 UTC
The back and forward buttons don't work the way they do in other applications (web browsers, nautilus,...). Consider an archive with the following directory structure: / /a /a/b /a/c After browsing from / to /a to /a/b, you press Back and get to /a. Browse to /a/c and press Back to /a. One would expect that pressing Back again would get you to the directory from which you first got to /a, which is /. Instead you end up in /a/b. The attached patch corrects the behavior to match nautilus, which deletes all forward history when you browse to a new location. Other information: Also reported at https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/354136
Created attachment 132594 [details] [review] Patch for file-roller 2.24.1 to make back/forward button behavior match nautilus
I’d like to try and provide a better explanation for the bug, from what I’ve gathered by blackbox-testing file-roller and nautilus Assume the back/forward history list is the following: file-roller nautilus 0: / 0: / 1: /a 1: /a *2: /a/b *2: /a/b with the marked item (2: /a/b) being the current view. Now, if Back is pressed, instead of just switching to history item 1, file-roller will currently create a new history entry with the same path as item 1: file-roller nautilus 0: / 0: / 1: /a *1: /a 2: /a/b 2: /a/b *3: /a Further navigating into /a/c thus leads to this: file-roller nautilus 0: / 0: / 1: /a 1: /a 2: /a/b *2: /a/c 3: /a *4: /a/c With the net result of having a very unintuitive (and long) back-navigation in file-roller.
It is still an issue with the latest release 3.6.1.1. Is there any chance that it will be fixed anytime soon?
This problem has been fixed in the development version. The fix will be available in the next software release (3.6.3). Thank you for your bug report.