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

Improve filer dialog auto-complete usability #2478

Open
3 tasks done
mtrezza opened this issue Jun 24, 2023 · 5 comments
Open
3 tasks done

Improve filer dialog auto-complete usability #2478

mtrezza opened this issue Jun 24, 2023 · 5 comments
Labels
bounty:$5 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature

Comments

@mtrezza
Copy link
Member

mtrezza commented Jun 24, 2023

New Feature / Enhancement Checklist

Current Limitation

#2463 introduced auto-complete in the filter dialog. However, it's usability should be improved. When opening the filter dialog, a key is pre-selected and needs to be manually deleted for the whole key list to become visible. This can be more time consuming than before the auto-complete feature was added.

Feature / Enhancement Description

Behavior when opening empty filter dialog (without any filter set), and when clicking on the "Add" button to add a new filter condition:

  • Auto-focus on key text field
  • Do not pre-select any field, i.e. the key text field should be empty and the whole key list should be visible
@parse-github-assistant
Copy link

parse-github-assistant bot commented Jun 24, 2023

Thanks for opening this issue!

  • 🎉 We are excited about your ideas for improvement!

@mtrezza mtrezza added type:feature New feature or improvement of existing feature bounty:$5 Bounty applies for fixing this issue (Parse Bounty Program) labels Jun 24, 2023
@mtrezza
Copy link
Member Author

mtrezza commented Jun 24, 2023

cc @patelmilanun

@patelmilanun
Copy link
Member

I intentionally added the default key for autocomplete. If we do not do it than we need to put some validation. The component itself doesn't have the validation so it need to be added externally.

Do you still want to go ahead with this? I mean if u click on the field the whole text will get selected anyway. It's just 1 keystroke more than the older version.

@mtrezza
Copy link
Member Author

mtrezza commented Jun 27, 2023

I'd expect by default seeing an empty text field with the whole list showing.

The pre-selection of the key is really arbitrary and chances are that in most cases its not the text field someone is looking for. Could you disable the 'apply' and 'save' buttons unless every field has a valid key selected? If that's too difficult, I would just clear the text field as soon as someone clicks into it.

I think the issue is that the dashboard is currently not very keyboard friendly. There's a lot of mouse action and that is always slower than keyword shortcuts. I would imagine at some point we get to the following scenario:

  1. Hit key F -> filter dialog opens; text field has focus automatically.
  2. Enter em -> fields email and email2 shows in list.
  3. Hit arrow down key -> field email is selected.
  4. Hit Enter key -> search filter is applied (like clicking the "Apply" button)

In order to get to that, it would be good if when you open the filter dialog, the text field gets focused and is empty, with the whole field list showing.

@mtrezza
Copy link
Member Author

mtrezza commented May 4, 2024

@Bhavyajain21 this may be interesting for you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bounty:$5 Bounty applies for fixing this issue (Parse Bounty Program) type:feature New feature or improvement of existing feature
Projects
None yet
Development

No branches or pull requests

2 participants