Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Lens] overflowing search phrase in the combobox of fields problem #106555

Closed
Tracked by #57706
mbondyra opened this issue Jul 22, 2021 · 3 comments
Closed
Tracked by #57706

[Lens] overflowing search phrase in the combobox of fields problem #106555

mbondyra opened this issue Jul 22, 2021 · 3 comments
Labels
enhancement New value added to drive a business result Feature:Lens impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@mbondyra
Copy link
Contributor

mbondyra commented Jul 22, 2021

Describe the feature:
When search phrase in the combobox of fields overflows the width of the container, we only show characters starting from the beginning of the string. That forces a user to guess the remaining characters.

Quoting @dej611 from:
##106285 (review)

Probably the only enhancement would be to have some a better handling of the highlight when all the text visible is already selected.

Say you have a list of long fields (these are from metricbeat-*), once you type enough to fill up with the Highlight component all the visible space, there's no much you can do to differentiate all these fields:

Screenshot 2021-07-22 at 11 04 35

Reaching that point you start either go to the field you know already, or guess type chars to get the one field you are looking for (for instance: is it .remove or delete? is it .deletecompare or deleteorcompare etc...).
It would be nice if the highlight behaviour was more right-aligned showing always at least non-highlighted letter so that you can better guess.

Proposed solution: display extra 3 characters from the right side for example (based on the example above):
...spike.namespace.client.del...

@botelastic botelastic bot added the needs-team Issues missing a team label label Jul 22, 2021
@tsullivan tsullivan added the Team:Visualizations Visualization editors, elastic-charts and infrastructure label Jul 26, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jul 26, 2021
@stratoula stratoula added Feature:Lens enhancement New value added to drive a business result labels Jul 26, 2021
@stratoula stratoula added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Jan 13, 2023
@stratoula
Copy link
Contributor

This is fair, we should check the average field names (from our integrations dashboards for example) and then decide a strategy

@stratoula stratoula added impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels May 26, 2023
@stratoula
Copy link
Contributor

This has been resolved in recent kibana versions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Lens impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

No branches or pull requests

4 participants