GNOME Bugzilla – Bug 675315
Cannot immediately right-click on first search result via keyboard
Last modified: 2017-08-17 14:59:37 UTC
Steps to reproduce: 1. Get into the Overview (Alt+F1) 2. Type a letter 3. Press Shift+F10 to open a context/right-click menu for the selected item Results: The menu appears but is associated with the search entry. Workaround: Press Right Arrow, Left Arrow, Shift+F10 and it works as expected. I'm not sure what the RightAnswer(tm) is. One can make a good case for the existing behavior: You haven't left the search entry and the caret is still visible within that entry. But on the flip side: The first item is selected, pressing Return from the search entry activates the first item, and pressing Tab from the search entry skips over the first item and moves you to the second item. Lastly, the workaround feels odd. <shrugs> As for why I'm filing it at all, it's potentially confusing for users who are blind.
I knew that having this "fake selection" stuff in the search results would be bad.
(In reply to comment #1) > I knew that having this "fake selection" stuff in the search results would be > bad. For the record, I didn't say that. :) This is just one of those edge cases.... They happen. Ya know, a possible solution occurred to me after filing this bug: In the situation described above, make Shift+F10 would apply to the same object as Return. Rationale (admittedly based on a certain amount of speculation): * The "typical" user uses the mouse to right-click. These users wouldn't notice the change. * The "typical" keyboard user copies and pastes with Ctrl+C and Ctrl+V respectively. For them, the menu that pops up in the entry isn't needed. * It would make the keyboard interaction (Return, Shift+F10) more consistent. * It should solve the problem for users who are blind. :)
Possible dupe of bug #679977 ? Maybe solved in 3.6? I'd need to test for a few weeks/months of "daily use" to be sure...
Seems like the context popup should open on the highlighted search result.
Hi, I am interested in working on this bug. So please can I get assigned for this bug and can anyone help me in fixing this bug? Regards, Anup
The bug is still reproducible. So, please can anyone help me with this bug?
Still happening in 3.24
Created attachment 357678 [details] [review] viewSelector: Open context for highlighted search result To make search more efficient, users don't need to move the actual keyboard focus away from the search entry to activate the first result. However the shift+f10 shortcut to pop up the context menu via keyboard still acts on the actually focused widget, which is the entry. It makes more sense to open the context menu of the selected result instead, as that's what's highlighted and responds to keyboard activation.
Review of attachment 357678 [details] [review]: looks fine ::: js/ui/search.js @@ +688,3 @@ + + if (this._defaultResult) + this._defaultResult.actor.emit('popup-menu'); st_widget_popup_menu() is public API that could be used instead
Attachment 357678 [details] pushed as 093b73b - viewSelector: Open context for highlighted search result Ah yes, indeed - updated patch before pushing.