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:
- open codesandbox
- open console
- press keyboard ArrowUp key
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)
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:
Context 🔦
Although it is not very important, I think it will confuse the user.
Your environment 🌎
`npx @mui/envinfo`