After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 753346 - Tab switching overwrites breadcrumbs when navigating back to same parent folder
Tab switching overwrites breadcrumbs when navigating back to same parent folder
Status: RESOLVED DUPLICATE of bug 670465
Product: nautilus
Classification: Core
Component: Tabs
3.20.x
Other Linux
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-08-07 08:35 UTC by hey
Modified: 2017-08-23 08:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description hey 2015-08-07 08:35:49 UTC 
Switching tabs in Nautilus also switches the breadcrumb accordingly. When navigating up to the same parent folder though, the child elements are overwritten in one of the tabs and you can’t easily navigate back down again.

Simple example for reproducing the issue:

* You have 2 (or more) tabs open in Nautilus with separate folders.
* Say you’re both in subfolders of home – »Projects« and »Personal«.
* So the first breadcrumb says »Home > Projects« and the second one »Home > Personal«.
* Now navigate up to »Home« from the Projects folder. Then navigate up to »Home« from the Personal folder as well.
* When you go back to the first tab where the »Projects« folder was, the breadcrumb will now say »Home > Personal« instead of »Home > Projects« as expected. The forward button on the left still works though to get back down into the correct »Projects« folder, so I assume the breadcrumb changing is a bug.
Comment 1 António Fernandes 2017-08-23 08:00:58 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 670465 ***