Behavior of Search-Box when selecting suggestions with keyboard
-
[screen-capture of the described behavior]For some time now there has been an annoying behavior / glitch when using the Search-Box (upper right) in Vivaldi.
If something is typed, (e.g. "vival") and then one of the suggestions from the drop-down (e.g. "vivaldi") is selected using the Arrow-Keys, upon submitting the search-query with the Enter-Key, the displayed text in the Search-Box reverts back to only the typed letters (e.g. "vival"). That is also what is then sent to the search engine.I observed that behavior on several windows machines and on Debian as well.
If this is (hopefully not) intended behavior, please include an option to have the usual functionality:
The query submitted to the Search-Engine is what was displayed in the search box before pressing the Enter-Key (e.g. "vivaldi"). That is also what should stay in the Search-Box after the search has been submitted. -
They fixed that in the snapshots already.
For now, just make the selection in the dropdown and add a space to the end before hitting Enter.
-
Yes, that is what I'm doing when I remember. It is annoying because it breaks routine.
But if it is fixed in the snapshots that's really good news. It persisted over many updates so I thought bringing it to attention might sensible. I think there was a phase some months ago where it submitted the full string, but retained only the typed string in the search box. (also not the behavior I would prefer).But thank you for this information, maybe I will try using the snapshot-channel again, or just wait until the fix makes it into stable.
-
In the newest snapshot (2.4.1476.4 (Offizieller Build) (64-Bit)) it's broken again in a new way: now there is no way of selecting and submitting a suggestion using only the keyboard. It just isn't transferred to the search-box.
-
@entity damn, again! it was fixed in previous snapshots.
http://iancoog.altervista.org/
--=[]=-----------------------------------------------------------------------=[]=--
Windows10 64bits - 8core i9-9900K @ 3.60GHz - 16Gb RAM - nVidia GT1030 -
@iAN-CooG Same in 1483.4. Can we assume this is known? I see no mention of it in the latest blog, even in comments.
-
I've re-reported it to be sure, it was fixed 3 weeks ago
https://vivaldi.com/blog/snapshots/control-tab-stacks-even-more-and-sync-bookmarks-bar-vivaldi-browser-snapshot-1462-4/
Summary: Search suggestions selected from search field drop-down are not populated in search engine (was VB-48886)
Key: VB-50744 -
@entity said in Behavior of Search-Box when selecting suggestions with keyboard:
In the newest snapshot (2.4.1476.4 (Offizieller Build) (64-Bit)) it's broken again in a new way: now there is no way of selecting and submitting a suggestion using only the keyboard. It just isn't transferred to the search-box.
Somehow, this fix
sneaked into the final 2.4 build(correction: it's actually the first 2.5 snapshot!). They had fixed the original problem some weeks back, but this new variant (no keyboard) was still there earlier this week.So, does anyone see anything else wrong in this area?
-
@rseiler search box now works on 2.5 snapshot, including shift-del for removing old searches; Down+enter sends correctly the suggestion to the search engine.
On the address bar dropdown tho, shift-del is still not working, only the "X" icon can be used with mouse to delete old typed entries.
The 2.4 release could have been delayed some hours and presented publically after including these fixes, but it's not my problem anymore, as I found the 2.5 snapshot announcement even before being able to test 2.4
-
(Vivaldi 2.6.1581.5 on Windows 10 )
This is still/again broken. Now arrow keys are ignored if Num-Lock or Caps-Lock is active.Why is this such a huge problem to fix?
-
@entity said in Behavior of Search-Box when selecting suggestions with keyboard:
This is still/again broken. Now arrow keys are ignored if Num-Lock or Caps-Lock is active.
Ah so it's due to NumLock being active, I see. I couldn't understand why someone else said Down Arrow worked for selecting engine. At least now I know :face_with_stuck-out_tongue_closed_eyes:
With NumLock on you can actually press Shift+Down Arrow to get the history and Tab will select. But it should be Arrow keys. And still can't delete entries with keyboard.
Also I believe the best would be to have Down Arrow to select history, and Shift+Down Arrow to select engine. Because using search history is usually the most common thing done, while selecting active engine is rarer.
