You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a user has "arrowed down" to highlight a field name/value suggestion, and the field name/value suggestion list (or the suggestions up to and including the highlighted field name/value) doesn't change, the highlighted name/value should not reset to the first item in the list.
Alternatively: if the user has highlighted a field name/value suggestion the suggestion list should not be modified/updated.
Current Behavior
Given I have fields source_priority, source_type, and source (among others), if I type so and arrow down to highlight source (skipping source_priority and source_type) I see the highlighted suggestion jump up to the first item in the list (presumably after /api/search/validate completes-- ~80ms). Something similar happens for field value suggestions.
I believe this started after we moved from 5.0.x to 5.1.x.
Steps to Reproduce (for bugs)
Have a 5.1.2 environment
Have fields with a common prefix
Open your browser dev tools and watch XHR requests
Start typing that field name prefix, and after the initial suggestions appear arrow down past the first entry and wait
Note that after the /api/search/validate request completes the first suggestions gets highlighted
Context
This makes working with field name/value suggestions annoying, since the UI wipes out the suggestion I arrowed down to.
Your Environment
Graylog Version: 5.1.2
Java Version: 17.0.7
Elasticsearch Version: 7.10.2
MongoDB Version: 5.0.14
Browser version: Firefox 114, Chrome 114
The text was updated successfully, but these errors were encountered:
Expected Behavior
If a user has "arrowed down" to highlight a field name/value suggestion, and the field name/value suggestion list (or the suggestions up to and including the highlighted field name/value) doesn't change, the highlighted name/value should not reset to the first item in the list.
Alternatively: if the user has highlighted a field name/value suggestion the suggestion list should not be modified/updated.
Current Behavior
Given I have fields
source_priority
,source_type
, andsource
(among others), if I typeso
and arrow down to highlightsource
(skippingsource_priority
andsource_type
) I see the highlighted suggestion jump up to the first item in the list (presumably after/api/search/validate
completes-- ~80ms). Something similar happens for field value suggestions.I believe this started after we moved from
5.0.x
to5.1.x
.Steps to Reproduce (for bugs)
5.1.2
environment/api/search/validate
request completes the first suggestions gets highlightedContext
This makes working with field name/value suggestions annoying, since the UI wipes out the suggestion I arrowed down to.
Your Environment
5.1.2
17.0.7
7.10.2
5.0.14
The text was updated successfully, but these errors were encountered: