'Open Folder' in Search for Files is a misleading option for folders and opens the parent directory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
One Hundred Papercuts |
Fix Released
|
Low
|
Andrew Fister | ||
gnome-utils |
Fix Released
|
Medium
|
|||
gnome-utils (Ubuntu) |
Fix Released
|
Low
|
Unassigned |
Bug Description
After using the standard graphical search tool in Ubuntu (Places > Search for files...) to search for files, you are shown a list of files and folders that match you description. Right-clicking on a file gives the option "Open" and "Open folder", which is very clear. The first will open the file, the second the containing folder.
Right-clicking on a folder will give the same two options, "Open" and "Open folder". But in this case these options are confusing, because "Open folder" sounds like it will open the folder you are looking at, but does not--it opens the containing folder. It has happened to me often that I click "Open folder" without thinking, and get to where I do not want to be.
All of the three following schemes seem clearer to me:
1. For folders, change "Open folder" to "Open containing folder".
2. For folders, change "Open" to "Open folder" and "Open folder" to "Open containing folder".
3. For folders, remove the option to open the containing folder altogether. (Unlike opening a file, opening a folder will take you the file manager anyway, where the containing folder is only a single mouseclick away.)
Related branches
- VCS imports: Pending requested
-
Diff: 1268 lines (+173/-161)76 files modifiedgsearchtool/gsearchtool-callbacks.c (+2/-2)
gsearchtool/help/C/gnome-search-tool.xml (+1/-1)
gsearchtool/help/ca/ca.po (+1/-1)
gsearchtool/help/cs/cs.po (+1/-1)
gsearchtool/help/de/de.po (+1/-1)
gsearchtool/help/el/el.po (+1/-1)
gsearchtool/help/en_GB/en_GB.po (+2/-2)
gsearchtool/help/es/es.po (+1/-1)
gsearchtool/help/eu/eu.po (+1/-1)
gsearchtool/help/fi/fi.po (+1/-1)
gsearchtool/help/fr/fr.po (+1/-1)
gsearchtool/help/it/it.po (+1/-1)
gsearchtool/help/ko/ko.po (+1/-1)
gsearchtool/help/oc/oc.po (+1/-1)
gsearchtool/help/ru/ru.po (+1/-1)
gsearchtool/help/sv/sv.po (+1/-1)
gsearchtool/help/uk/uk.po (+1/-1)
gsearchtool/help/zh_CN/zh_CN.po (+1/-1)
po/af.po (+2/-2)
po/as.po (+23/-13)
po/bg.po (+2/-2)
po/bn.po (+2/-2)
po/bn_IN.po (+2/-2)
po/br.po (+2/-2)
po/ca.po (+2/-2)
po/ca@valencia.po (+2/-2)
po/crh.po (+2/-2)
po/cs.po (+2/-2)
po/da.po (+2/-2)
po/de.po (+2/-2)
po/el.po (+2/-2)
po/en@shaw.po (+2/-2)
po/en_GB.po (+3/-3)
po/eo.po (+2/-2)
po/es.po (+2/-2)
po/et.po (+2/-2)
po/eu.po (+2/-2)
po/fi.po (+2/-2)
po/fr.po (+2/-2)
po/ga.po (+3/-3)
po/gl.po (+2/-2)
po/gu.po (+4/-4)
po/he.po (+2/-2)
po/hi.po (+4/-4)
po/hu.po (+2/-2)
po/id.po (+2/-2)
po/it.po (+2/-2)
po/ja.po (+2/-2)
po/kn.po (+4/-4)
po/ko.po (+2/-2)
po/lt.po (+2/-2)
po/lv.po (+3/-3)
po/ml.po (+4/-4)
po/mr.po (+4/-4)
po/nb.po (+2/-2)
po/nds.po (+2/-2)
po/nl.po (+2/-2)
po/or.po (+2/-2)
po/pa.po (+2/-2)
po/pl.po (+2/-2)
po/pt.po (+2/-2)
po/pt_BR.po (+2/-2)
po/ro.po (+2/-2)
po/ru.po (+2/-2)
po/sl.po (+4/-2)
po/sr.po (+2/-2)
po/sr@latin.po (+2/-2)
po/sv.po (+2/-2)
po/ta.po (+2/-2)
po/te.po (+2/-2)
po/th.po (+2/-2)
po/tr.po (+3/-3)
po/uk.po (+2/-2)
po/zh_CN.po (+2/-2)
po/zh_HK.po (+2/-2)
po/zh_TW.po (+2/-2)
summary: |
- Open folder option in Search dialogue is misleading for folders + 'Open Folder' in Search for Files is a misleading option for folders and + opens the parent directory |
Changed in gnome-utils (Ubuntu): | |
importance: | Undecided → Low |
Changed in gnome-utils (Ubuntu): | |
status: | New → Triaged |
Changed in gnome-utils: | |
status: | Unknown → New |
Changed in hundredpapercuts: | |
status: | Triaged → In Progress |
assignee: | nobody → Andrew Fister (andrewfister) |
Changed in gnome-utils: | |
importance: | Unknown → Medium |
Changed in gnome-utils: | |
status: | New → Confirmed |
Changed in gnome-utils: | |
status: | Confirmed → Fix Released |
Changed in gnome-utils (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in hundredpapercuts: | |
status: | Fix Committed → Fix Released |
I'm accepting this as a papercut as this is indeed a usability issue that shouldn't be too hard to fix. Thank you for taking the time to report this issue and providing us with three possible solutions.
Not to people willing to fix this issue: please make sure to fix this early in the cycle as not to upset the translators and the release manager by violating the freezes.