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 640779 - Keyboard navigation in search results with left/right arrow keys
Keyboard navigation in search results with left/right arrow keys
Status: RESOLVED DUPLICATE of bug 663901
Product: gnome-shell
Classification: Core
Component: general
2.91.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
: 648089 649720 653094 654787 658081 669614 669714 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-01-27 22:46 UTC by António Lima
Modified: 2012-02-09 01:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description António Lima 2011-01-27 22:46:35 UTC
Right now to navigate in the search results in overview is only possible with up/down arrow keys. I find myself always trying to navigate with left/right to go to the next application.

I think it's not intuitive to navigate only with up/down.
Comment 1 Rui Matos 2011-02-17 22:51:18 UTC
Dupe of bug 618887.
Comment 2 Dan Winship 2011-02-23 18:40:19 UTC
We need design input here.

If we want to keep the current "split focus", then the left and right arrow keys are ambiguous between "move the app selection" and "move the cursor in the search entry", and either way some people will be confused/annoyed.

Alternatively, we could have "normal" focus, where you'd have to use Tab or Down arrow to get out of the entry into the list of results (but Return could still activate the first item anyway, and we could also make it so that typing an alphabetic key would automatically move the focus back to the entry).
Comment 3 António Lima 2011-02-23 22:35:04 UTC
Personally I find the second behavior more intuitive and less pron to confusion. If you just want to navigate in the apps with the arrow keys just hit Tab and do the rest of the navigation there. I think people won't usually go back to the search entry after navigating. At least not before launching the app they where looking for.

If you want to go back to the search entry, just hit Tab again.
 
Just an opinion of a user :).
Comment 4 Dan Winship 2011-04-18 20:15:11 UTC
*** Bug 648089 has been marked as a duplicate of this bug. ***
Comment 5 Xavier Claessens 2011-04-18 20:35:05 UTC
When filling bug #648089 I did not discover up/down was selecting icones. However I've intuitively tried with tab, I would vote for tab to switch focus between entry->icons->google->wikipedia->entry->etc...
Comment 6 David Prieto 2011-04-24 01:26:25 UTC
I agree with António. Search can return many results, and navigating them one by one may become extremely clumsy. I think that case is more usual, and outweighs, the convenience of moving left and right after performing a search.
Comment 7 Tarin Mahmood 2011-05-03 07:15:37 UTC
Why I can't use arrow keys to navigate the search result? It feels more common sense and convenient. 

Its irritating when I search for something, say keyboard, which is in the second row of the results after typing the first 3 chars and I have to press down arrow 4 times (possibly more or less depending on the applications having similar combination) then enter. with the normal navigation method I only need to type 'k' then down arrow and enter

8 vs 3 key strokes
Comment 8 Florian Müllner 2011-05-08 10:47:00 UTC
*** Bug 649720 has been marked as a duplicate of this bug. ***
Comment 9 Michael Trunner 2011-05-08 10:54:07 UTC
I think nobody is using the arrow key in a search field. Most people will using backspace and rewrite the complete search input. So arrow key can be used the whole time for navigation in the search result.
Comment 10 Tarin Mahmood 2011-05-08 15:02:12 UTC
^ definitely, also as tab is unused, it can be used to move in between sections, like applications > settings, settings > files etc. It would be simple and expected behavior so user can use it without thinking too much.
Comment 11 William Jon McCann 2011-06-07 21:18:04 UTC
How about just requiring a single down press in order to key focus the first search result and then nav in 2d as usual?
Comment 12 Dan Winship 2011-06-09 14:24:19 UTC
(In reply to comment #11)
> How about just requiring a single down press in order to key focus the first
> search result and then nav in 2d as usual?

Yeah, that's what I meant about "normal focus" above.

The only remaining issue is, is there any visual indication that typing Return will activate the first item? That would require having some highlight there that was distinct from the focus highlight.
Comment 13 Milan Bouchet-Valat 2011-06-21 10:57:46 UTC
*** Bug 653094 has been marked as a duplicate of this bug. ***
Comment 14 Owen Taylor 2011-07-18 14:52:25 UTC
*** Bug 654787 has been marked as a duplicate of this bug. ***
Comment 15 Geoffroy 2011-07-18 17:49:57 UTC
I think switching focus using tab would be cumbersome.
I'd rather forget about moving the cursor in the search field (backspace is enough), use the arrows to navigate, and use tab (or PgUp/PgDown) to cycle between applications / settings / files
Comment 16 Florian Müllner 2011-09-02 18:34:24 UTC
*** Bug 658081 has been marked as a duplicate of this bug. ***
Comment 17 Michael Kanis 2011-09-20 14:15:03 UTC
The icon view takes up almost all the space on the screen and the search field is relatively small and "hidden" in the upper right corner. The first few times I used the search, I didn't even notice that there was a separate text entry field.

For this reason I think it would be most intuitive to navigate in the icons with the arrow keys right away, without having to think of focus changing or stuff like that.

Design wise perhaps it could be something similar to what Gnome-Do did? It just highlights the input in the search result. I couldn't find a decent video that demonstrates what I mean, but you can probably tell from the screenshot(s) on http://do.davebsd.com/
Comment 18 Rui Matos 2011-11-30 17:34:34 UTC
I'm sorry, I didn't find this bug when submitting patches to fix this issue. I'll mark this bug as a dupe of the one I created which has patches.

*** This bug has been marked as a duplicate of bug 663901 ***
Comment 19 Jasper St. Pierre (not reading bugmail) 2012-02-07 22:30:43 UTC
*** Bug 669614 has been marked as a duplicate of this bug. ***
Comment 20 Florian Müllner 2012-02-09 00:31:55 UTC
*** Bug 669714 has been marked as a duplicate of this bug. ***