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

[Autocomplete] ArrowUp must be pressed twice to bypass disabled items above #32280

Open
2 tasks done
ccpu opened this issue Apr 13, 2022 · 2 comments
Open
2 tasks done
Labels
accessibility a11y component: autocomplete This is the name of the generic UI component, not the React module! new feature New feature or request

Comments

@ccpu
Copy link

ccpu commented Apr 13, 2022

Duplicates

  • I have searched the existing issues

Latest version

  • I have tested the latest version

Current behavior 😯

When the first item is disabled, the ArrowUp must be pressed twice to bypass the disabled item.

Expected behavior 🤔

It's not clear if it is a bug or if it was designed this way, but my logic says that if an item is disabled, then ArrowUp should bypass it.

Steps to reproduce 🕹

Steps:

  1. open codesandbox
  2. open console
  3. press keyboard ArrowUp key

Autocomplete-Issue

Context 🔦

Although it is not very important, I think it will confuse the user.

Your environment 🌎

`npx @mui/envinfo`
 System:
    OS: Windows 10 
  Binaries:
    Node: 14.17.0 
    Yarn: 1.22.10 
    npm: 6.14.13
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.19041.1266.0), Chromium (100.0.1185.36)
@ccpu ccpu added the status: waiting for maintainer These issues haven't been looked at yet by a maintainer label Apr 13, 2022
@hbjORbj hbjORbj added new feature New feature or request component: autocomplete This is the name of the generic UI component, not the React module! accessibility a11y and removed status: waiting for maintainer These issues haven't been looked at yet by a maintainer labels Apr 13, 2022
@hbjORbj
Copy link
Member

hbjORbj commented Apr 13, 2022

Hi. Thanks for opening the issue.

I personally agree with you but I think this can be quite debatable.

If you are willing to open a pull request for this, please go ahead and feel free to request a review from the core team including myself.

@ccpu
Copy link
Author

ccpu commented Apr 14, 2022

Thanks for the response. If I get a chance, I will investigate this further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility a11y component: autocomplete This is the name of the generic UI component, not the React module! new feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants