JedWatson / JedWatson/react-select
Option order is wrong with nested options
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 28k
- Forks
- 4.1k
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I have this code snippet
<RichSelect
onChange={onInputChange}
options={[
{ label: "foo", value: "foo" },
{ label: "i am disabled", value: "who care", disabled: true },
{ label: "bar", value: 2 },
{ label: "Primary Colors",
options: [
{ label: "Yellow", value: "yellow" },
{ label: "Red", value: "red" },
{ label: "Blue", value: "blue" }
]
}
]}
/>.
The mac voice over is giving wrong output for "Yellow" option as """Yellow focused, 0 of 4""". I don't see problem when there is not nested optiosn in rich-select. I tried with 4.3.1 still it is giving wrong order. Any pointers?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the provided RichSelect example with nested options and macOS VoiceOver. Trace how the nested "Yellow" option is announced and ordered; done means VoiceOver reports its correct position instead of "0 of 4".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100