-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
UI consistency - refresh button #3321
Comments
I'd rather get rid of the refresh button on visualize. I don't like the clutter in that bar |
I'd rather have it replaced with a settings icon from where it's possible to use another index, just like in discover. Right now this has to be done manually in settings. I never used the refresh button, but switching index happens quite often. |
Another option is to change the search icon to refresh once the results have been returned, but switch it back to search as soon as the search is edited. This is similar behaviour to the Firefox address bar. |
Just another thought, having a refresh button will ensure users don't opt for clicking the browser refresh button, getting a different routing preference for their new session id and then potentially seeing inconsistent results? |
We discussed that as the design team thinks about the header re-design, they should consider a consistent way to refresh across the UI: #9144 Removing the "discuss" label, since this is something we should do. |
This is planned and in the works with the new header. We have several tickets tracking the reactification and UI of the datepicker and how queries are shown in dirty / updated states. You can play around with the functionality in EUI here. |
The refresh button currently only exists in the Visualize page, for when a saved search is being used and the search button is disabled. However, I personally think it would be better for new users if the refresh button existed in discover, visualize and dashboard for consistency, and is more obvious than clicking the search button. Happy to do the PR. Thoughts?
The text was updated successfully, but these errors were encountered: