Bug report did not expire due to bug watch and assignment
Upstream report closed "RESOLVED INCOMPLETE" on 2010-09-09 as requested
information was not provided
Can't reproduce here using nautilus 3.26.4 and Ubuntu 18.04
No response to comment #8 over a year ago so closing
** Changed in: nautilus (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned)
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/404779
Title:
Nautilus "search when typing" behaviour is inconsistent
Status in One Hundred Papercuts:
Invalid
Status in Nautilus:
Expired
Status in nautilus package in Ubuntu:
Invalid
Bug description:
By default, Nautilus will perform a search/select files in the folder
as users type into the window, like Firefox's quick find. However it
seems to activate rather inconsistently when using the side panes.
E.g.
1. Sometimes when opening the Nautilus window the folder view is not
selected, so typing into the window does nothing. The tiny search box
still pops up as if reassuring the user that it is searching, but
nothing appears to be selected.
2. As an example of 1, if the user opens a folder by clicking on a
Places bookmark on the left pane then starts typing, it doesn't
actually work as the left pane is still highlighted. The only direct
visual cue that tells the user that it's not working is the tiny
search box that pops up on the left instead of the right, but it's too
minor. (The fact that the Places pane doesn't support type-searching
compared to Tree and History should also be considered a bug too.)
3. As an example of 1, if the user uses the crumbs buttons in the
Location bar, the Go menu, the Bookmarks menu, or selecting tabs,
typing into the window doesn't even show the tiny search box.
4. Hitting tab when the user notices problem 2 solves the problem, but
requires domain knowledge of the tabbing order of panels in nautilus,
and also may require multiple tab presses in problem 3 for example.
Pressing the up-down key when problem 3 is noticed also immediately
reminds the user where the control is being focused, but requires
extra time to discover that and manually target the folder view again,
and may also disrupt the current folder view depending on the control
selected. (There's also another bug here, where after when the folder
view is finally selected by tabbing and the user starts typing, it
appears the tiny search box text is not cleared and will just show the
junk text from the user's previous search attempts)
Suggested fixes:
- Based on these use cases, allow switching the focus to the folder pane when
the user starts typing into the window.
- Alternatively, make the visual cues more noticeable when users start typing
in the window if another control other than the folder view is selected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/404779/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
