Files issueshttps://gitlab.gnome.org/GNOME/nautilus/-/issues2019-01-14T12:37:58Zhttps://gitlab.gnome.org/GNOME/nautilus/-/issues/765DnD in pathbar uses old style2019-01-14T12:37:58ZCarlos SorianoDnD in pathbar uses old style@calamandrei sent me an email:
Nautilus pathbar needs
custom styling when the pathbar buttons are dnd drop targets: the
green outline (we use all over the place) needs to go, having a thick
green bottom border there would do (with the i...@calamandrei sent me an email:
Nautilus pathbar needs
custom styling when the pathbar buttons are dnd drop targets: the
green outline (we use all over the place) needs to go, having a thick
green bottom border there would do (with the inherited green text
color from the generic dnd target styling)GNOME 3.30https://gitlab.gnome.org/GNOME/nautilus/-/issues/639Folders not expanding with arrow keys2023-05-28T22:43:07ZGhost UserFolders not expanding with arrow keysIn GNOME nautilus 3.30.0, it is no longer possible for me to "browse" through folders using arrow keys (right to open a folder, left to close a folder), but I either have to enter a folder or use my mouse to press the arrow on the left s...In GNOME nautilus 3.30.0, it is no longer possible for me to "browse" through folders using arrow keys (right to open a folder, left to close a folder), but I either have to enter a folder or use my mouse to press the arrow on the left side.
Please fix that to make nautilus more accessable by keyboard again.GNOME 3.30António Fernandesantoniof@gnome.orgAntónio Fernandesantoniof@gnome.orghttps://gitlab.gnome.org/GNOME/nautilus/-/issues/610Can't select search results with keyboard (regression from 3.28 to 3.30)2018-10-03T08:22:28ZAntónio Fernandesantoniof@gnome.orgCan't select search results with keyboard (regression from 3.28 to 3.30)# Steps to reproduce
1. Type to search.
2. Press the arrow down key.
# Expected behavior (and 3.12 behavior)
* Focus changes to files view.
* Second search result is selected (assuming list view).
# 3.28 and earlier behavior
* Focus...# Steps to reproduce
1. Type to search.
2. Press the arrow down key.
# Expected behavior (and 3.12 behavior)
* Focus changes to files view.
* Second search result is selected (assuming list view).
# 3.28 and earlier behavior
* Focus changes to files view.
* First search result remains selected. Must press arrow down again to select 2nd result.
# Current behavior (3.30.0)
* Nothing happens. Focus remains in the search entry.
* Available keyboard-only alternative is pressing [Tab] at least 17 times.
In practice, one is forced to use a pointing device, which is not convenient because the hands were already on the keyboard from typing the search query.
# Comment
This may need a more proper fix going forward with Gtk+4. More context in #385.
But for 3.30 it would be nice to fix the regression from 3.28.GNOME 3.30https://gitlab.gnome.org/GNOME/nautilus/-/issues/598pathbar: middle click on directory part no longer opens a new tab2018-08-28T17:47:24ZChristoph Reiterpathbar: middle click on directory part no longer opens a new tab1) Go to some sub directory
2) Middle click on any of the directory parts in the path bar
Expected:
3) A new tab opens for the clicked directory
Actual:
3) The current view is changed to that directory like with a left click1) Go to some sub directory
2) Middle click on any of the directory parts in the path bar
Expected:
3) A new tab opens for the clicked directory
Actual:
3) The current view is changed to that directory like with a left clickGNOME 3.30https://gitlab.gnome.org/GNOME/nautilus/-/issues/595search started with ctrl+f can't be canceled with escape2018-08-28T10:30:59ZChristoph Reitersearch started with ctrl+f can't be canceled with escapeUsing 3.29.90.1
1. press ctrl+f
2. press escape
Expected:
3. path bar shown again
Actual:
3. search entry is still visibleUsing 3.29.90.1
1. press ctrl+f
2. press escape
Expected:
3. path bar shown again
Actual:
3. search entry is still visibleGNOME 3.30https://gitlab.gnome.org/GNOME/nautilus/-/issues/570Search button and search entry state can get out of sync2023-06-08T23:19:46ZGhost UserSearch button and search entry state can get out of sync# Steps to reproduce
## Case A
1. Press the search button (while the search entry is hidden)
2. Enter a search term
3. Press the clear button at the end of the search entry
## Case B
1. Press Ctrl+F (while the search entry is hidden)
2....# Steps to reproduce
## Case A
1. Press the search button (while the search entry is hidden)
2. Enter a search term
3. Press the clear button at the end of the search entry
## Case B
1. Press Ctrl+F (while the search entry is hidden)
2. Press Escape
Reproducible in:
- Flatpak unstable: yes
# Current behavior
## Case A
The search button stays pressed, but the search entry is hidden. You now need to press the search button twice to display the search entry again.
## Case B
The search button does not appear pressed. Pressing Escape does nothing. You now need to press the search button twice to hide the search entry again.
# Expected behavior
## Case A
The search button no longer appears pressed.
## Case B
The search button appears pressed. Escape hides the search entry.
<!-- Ignore the text under this line. -->GNOME 3.30António Fernandesantoniof@gnome.orgAntónio Fernandesantoniof@gnome.orghttps://gitlab.gnome.org/GNOME/nautilus/-/issues/569Hamburger menu is not accessible via keyboard2018-08-26T14:40:41ZGhost UserHamburger menu is not accessible via keyboard# Steps to reproduce
1. Use the Tab key to try and focus the hamburger menu OR press F10
Reproducible in:
- Flatpak unstable: yes
# Current behavior
The hamburger menu is never focused when pressing Tab (if the arrow button to the left...# Steps to reproduce
1. Use the Tab key to try and focus the hamburger menu OR press F10
Reproducible in:
- Flatpak unstable: yes
# Current behavior
The hamburger menu is never focused when pressing Tab (if the arrow button to the left of it is focused, the focus jumps to the sidebar). Pressing F10 opens the menu of the arrow button to the left of the hamburger menu.
# Expected behavior
I don’t know the intended design, but it seems to me that at least one of the methods should allow me to open the menu.
# Additional information
Maybe I am not aware of another method of the opening the menu via keyboard.
<!-- Ignore the text under this line. -->GNOME 3.30https://gitlab.gnome.org/GNOME/nautilus/-/issues/568Pathbar buttons cannot be activated via keyboard2018-08-24T15:47:06ZGhost UserPathbar buttons cannot be activated via keyboard# Steps to reproduce
1. Use Tab key to focus one of the buttons in the pathbar
2. Press Enter or Space
Reproducible in:
- Flatpak unstable: yes
# Current behavior
Nothing happens.
# Expected behavior
The location is visited or the me...# Steps to reproduce
1. Use Tab key to focus one of the buttons in the pathbar
2. Press Enter or Space
Reproducible in:
- Flatpak unstable: yes
# Current behavior
Nothing happens.
# Expected behavior
The location is visited or the menu for the current location is opened (same action as clicking one of the buttons does).
<!-- Ignore the text under this line. -->GNOME 3.30António Fernandesantoniof@gnome.orgAntónio Fernandesantoniof@gnome.orghttps://gitlab.gnome.org/GNOME/nautilus/-/issues/567Pathbar for trash looks odd2018-08-27T13:14:19ZGhost UserPathbar for trash looks oddThe pathbar for the trash has a slash instead of an icon at the start, unlike the other locations. See the attached screenshot.
![trash-bug](/uploads/1a5c1b31f534094e066ac61913d7385f/trash-bug.png)
Using the unstable flatpak.The pathbar for the trash has a slash instead of an icon at the start, unlike the other locations. See the attached screenshot.
![trash-bug](/uploads/1a5c1b31f534094e066ac61913d7385f/trash-bug.png)
Using the unstable flatpak.GNOME 3.30Leesoo Ahnlsahn@ooseel.netLeesoo Ahnlsahn@ooseel.nethttps://gitlab.gnome.org/GNOME/nautilus/-/issues/563Preferences: unintentional changes to UI file2018-08-29T08:23:18ZSebastian KellerPreferences: unintentional changes to UI fileCommit f2061e94093a33072e792181433b0618bf68d1b2 seems to have included several unintentional changes to the UI file. First, it removes the `border-width` property from the box which results in a padding around the content of the window. ...Commit f2061e94093a33072e792181433b0618bf68d1b2 seems to have included several unintentional changes to the UI file. First, it removes the `border-width` property from the box which results in a padding around the content of the window. Secondly, it removes the `accessible-role` properties which only got added a few months ago in commit 8c9203d6a8fa5622c739261c5c59bd56c9c7f0f6. The latter seems to be due to [bug 794518](https://bugzilla.gnome.org/show_bug.cgi?id=794518).GNOME 3.30António Fernandesantoniof@gnome.orgAntónio Fernandesantoniof@gnome.orghttps://gitlab.gnome.org/GNOME/nautilus/-/issues/553Can't rename2018-07-26T20:23:28ZAntónio Fernandesantoniof@gnome.orgCan't rename# Steps to reproduce
1. Select a file or folder
2. Click "Rename" in the context menu, or use the `F2` keyboard shortcut
3. Type a new name
Reproducible in:
- Flatpak unstable
- JHBuild git master
# Current behavior
Closes rename pop...# Steps to reproduce
1. Select a file or folder
2. Click "Rename" in the context menu, or use the `F2` keyboard shortcut
3. Type a new name
Reproducible in:
- Flatpak unstable
- JHBuild git master
# Current behavior
Closes rename popover and searches instead.
# Expected behavior
Types new name.GNOME 3.30https://gitlab.gnome.org/GNOME/nautilus/-/issues/552Some actions in the Current Location menu are broken2018-08-28T12:53:16ZAntónio Fernandesantoniof@gnome.orgSome actions in the Current Location menu are broken* [ ] "Add to Bookmark" doesn't work. It seems to link to a `view.bookmark` action, which doesn't exist.
* [ ] "Star" stars the file selected in the view, not the current location. But I think this should be removed, because we can't s...* [ ] "Add to Bookmark" doesn't work. It seems to link to a `view.bookmark` action, which doesn't exist.
* [ ] "Star" stars the file selected in the view, not the current location. But I think this should be removed, because we can't see if the current folder is starred or not unless we go to parent, and we can star it from there.
* [ ] "Unstar" (see above)
* [x] Extensions -- I did not test, but we need to confirm that they apply to the current location and not the file selected in the view.GNOME 3.30António Fernandesantoniof@gnome.orgAntónio Fernandesantoniof@gnome.orghttps://gitlab.gnome.org/GNOME/nautilus/-/issues/5483.29.x UI review2020-05-15T09:37:47ZAllan Day3.29.x UI reviewThis is a quick review of UI changes that have happened in the 3.29.x cycle, primarily the new location bar and header bar arrangement.
**Location/search bar width**
![3-30-path](/uploads/f6ace97637c4d415f47d1718dbabe4fb/3-30-path.png)...This is a quick review of UI changes that have happened in the 3.29.x cycle, primarily the new location bar and header bar arrangement.
**Location/search bar width**
![3-30-path](/uploads/f6ace97637c4d415f47d1718dbabe4fb/3-30-path.png)
The path and search bar can get very wide. This can be particularly odd in the search case - after tracking across to the right to press the search button, the user then has to track all the way across to the left to input their search text.
I'd consider constraining the width of the bar.
**Location bar layout**
![Screenshot_from_2018-07-25_09-38-07](/uploads/d81f31eaaf2d7be2730fb9fb6f306f52/Screenshot_from_2018-07-25_09-38-07.png)
Why the gap at the beginning of the location bar? It looks a little odd.
**Location bar highlight**
The blue underline below the current location. Since the path only extends as far as the current location, I'm not sure that the highlight is necessary.
Also, the highlight is displayed inconsistently. Click the current location to view the popover for the current location, and it sometimes disappears.
**Menu tooltip**
![Screenshot_from_2018-07-25_09-40-57](/uploads/a5c3f2eb49036a2207383bb2d4532289/Screenshot_from_2018-07-25_09-40-57.png)
I don't think you need a tooltip that says "open menu". Also, it obscures the menu when it's open.
**Primary menu**
![Screenshot_from_2018-07-25_09-43-43](/uploads/524abab9926defdb8a443f2a111d883b/Screenshot_from_2018-07-25_09-43-43.png)
The inclusion of Preferences, Help and About is a bit non-standard at this point. My preference would have been to have kept the view options as part of the hamburger menu this cycle, and then switched to the current menu arrangement next cycle, as we did the mass app menu migration.
However, if you are going to stick with the current arrangement, I'd add the keyboard shortcuts item too.
Thoughts on any of this, @jimmac?GNOME 3.30https://gitlab.gnome.org/GNOME/nautilus/-/issues/475Properties of current location are not displayed if items are selected.2018-06-14T12:39:52ZAntónio Fernandesantoniof@gnome.orgProperties of current location are not displayed if items are selected.# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Select on item from nautilus main view.
2. Click on the path bar to open the location menu.
3. From the location menu, click "Properties...# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Select on item from nautilus main view.
2. Click on the path bar to open the location menu.
3. From the location menu, click "Properties".
Reproducible in:
<!--
Please test if the issue was already fixed in the unstable version of the app.
For that, follow these steps:
1. Make sure Flatpak is installed or install it following these steps https://flatpak.org/setup
2. Install the unstable version of the app following this link
https://git.gnome.org/browse/gnome-apps-nightly/plain/nautilus.flatpakref
If these steps failed, write in 'Other' the distribution you’re using and
the version of the app.
Write yes or no after the semicolon.
-->
- Flatpak unstable
# Current behavior
<!-- Describe the current behavior. -->
A Properties window for the selected (child) item is displayed.
# Expected behavior
<!-- Describe the expected behavior. -->
A Properties window for the current location is displayed.
# Additional information
<!--
Provide more information that could be relevant.
If the issue is a crash, provide a stack trace following the steps in:
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces
-->
If no item is selected, it works as expected.GNOME 3.30https://gitlab.gnome.org/GNOME/nautilus/-/issues/473Google native files are no more opened in web browser2018-10-12T09:26:04ZOndrej HolyGoogle native files are no more opened in web browser`gvfsd-google` uses `G_FILE_TYPE_SHORTCUT` for native files with `G_FILE_ATTRIBUTE_STANDARD_TARGET_URI` set to the official location on the web. It is a bit tricky, however, it used to work nicely. The web browser used to be opened after...`gvfsd-google` uses `G_FILE_TYPE_SHORTCUT` for native files with `G_FILE_ATTRIBUTE_STANDARD_TARGET_URI` set to the official location on the web. It is a bit tricky, however, it used to work nicely. The web browser used to be opened after click on the native file. Currently, you get `Could not display ...; There is no application installed for "application/vnd.google-apps..." files.` error from `nautilus-3.28.1-1.fc28.x86_64`. No such desktop application obviously exists for the Google proprietary formats. But it doesn't work even if I modify the google backend sources to change the content type to `text/html`. Consequently, the web browser is opened, but not the target URI as it used to be before, but `file:///run/user/.../gvfs/google-drive:host=...,user=.../...`, which doesn't work...
Any idea what should be done to make this work again?
It corresponds with https://gitlab.gnome.org/GNOME/nautilus/issues/448 a bit.GNOME 3.30Carlos SorianoCarlos Sorianohttps://gitlab.gnome.org/GNOME/nautilus/-/issues/425More aggressive folder name truncation in the path-bar2018-07-26T12:24:46ZMaoschanzMore aggressive folder name truncation in the path-bar# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Create a folder with a long name (around 50 characters)
2. Open it
3. Try to resize or tile the window
Reproducible in:
* Flatpak unst...# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Create a folder with a long name (around 50 characters)
2. Open it
3. Try to resize or tile the window
Reproducible in:
* Flatpak unstable
* 3.22 to 3.26.x
# Current behavior
Even with the "only close button" layout that no one use, window tiling is prevented by the current folder name if it is long https://i.imgur.com/AupOIIV.png
(here, using a 1366×768 screen)
# Expected behavior
Folder name truncation should be more aggressive.
This could be compensated by showing the full name of the folder as a tooltip.
<!-- Ignore the text under this line. -->GNOME 3.30https://gitlab.gnome.org/GNOME/nautilus/-/issues/414Superfluous slash label on the file system root2018-07-26T17:32:26ZAntónio Fernandesantoniof@gnome.orgSuperfluous slash label on the file system rootWhen viewing a child directory of the root directory (such as "/home") there are 2 slashes ("/ /"):
![doubledash](/uploads/6ffd9f2bea26445b9c17e5b0a80efaee/doubledash.png)
Even when viewing the root dir itself, it is obnoxious because...When viewing a child directory of the root directory (such as "/home") there are 2 slashes ("/ /"):
![doubledash](/uploads/6ffd9f2bea26445b9c17e5b0a80efaee/doubledash.png)
Even when viewing the root dir itself, it is obnoxious because the icon, the slash and the disclosure arrow are 3 symbols in a row. This looks hieroglyphic.
![threesymbols](/uploads/990b5b5a10a4c39e8de6e02330f5ea9c/threesymbols.png)
For reference, this is how the root dir looked like in 3.28:
![328oldpathbar](/uploads/f82f20bce3b1faa03126dad4d447c318/328oldpathbar.png)
I think this was introduced by commit e759e82386f80fb214a420b789b07a194480462c, which has made it so that the root directory has a non-NULL label for the location name to avoid a crash.
I can think of 2 solutions:
1. Find another fix for the crash and revert the root directory to a single icon without a label.
2. Give the root directory a better name than "/".GNOME 3.30António Fernandesantoniof@gnome.orgAntónio Fernandesantoniof@gnome.orghttps://gitlab.gnome.org/GNOME/nautilus/-/issues/405Expand path bar button menu to include extensions menu items2019-12-29T21:06:07ZCarlos SorianoExpand path bar button menu to include extensions menu itemsIt's part of the benefits of the new design, but I didn't get to it.
![image](/uploads/5bf3ea49780c51b7f860a199bb017b26/image.png)It's part of the benefits of the new design, but I didn't get to it.
![image](/uploads/5bf3ea49780c51b7f860a199bb017b26/image.png)GNOME 3.30https://gitlab.gnome.org/GNOME/nautilus/-/issues/404Remove pathbar sliders?2018-07-25T21:12:31ZCarlos SorianoRemove pathbar sliders?With the new toolbar and path bar design the sliders look quite out of place, and it feels they don't really serve much use... at least the UX interaction is horrible.
We would still allow scrolling to navigate through the hierarchy, bu...With the new toolbar and path bar design the sliders look quite out of place, and it feels they don't really serve much use... at least the UX interaction is horrible.
We would still allow scrolling to navigate through the hierarchy, but that wouldn't be accessible to touch. But to be honest, not sure we should give much attention to the sliders with the current status for touch either.GNOME 3.30https://gitlab.gnome.org/GNOME/nautilus/-/issues/403"Searching locations only" makes the header bar bigger2018-07-14T08:13:21ZCarlos Soriano"Searching locations only" makes the header bar biggerThis is something to figure still out for the new header bar design. Right now it looks like:
![image](/uploads/83d90b816a437e6d35da25dfa486a668/image.png)This is something to figure still out for the new header bar design. Right now it looks like:
![image](/uploads/83d90b816a437e6d35da25dfa486a668/image.png)GNOME 3.30