Skip to content

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

@ccpu

Description

@ccpu

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    accessibilitya11yscope: autocompleteChanges related to the autocomplete. This includes ComboBox.type: new featureExpand the scope of the product to solve a new problem.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions