interestfor cascade issue
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
Hello,
I've been trying to use the new interestfor feature, but found a subtle edge case that seems to have been overlooked by the spec. You can reproduce the issue here: https://codepen.io/bakura10/pen/RNavdPL
As you can see from this example, the first command open a dialog which automatically move the focus to the first focusable element. If this element itself also has an interestfor attribute, then the interest listener will be called, even though there is technically no interest in the button (it is just focused automatically due to the very nature of dialog).
This is a frequent situation when using nested menu. Please note that it seems that native popover does not suffer this issue, but as we have a hard requirement to support iOS 15, we can't use popover for now.
Thanks!
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 with the CodePen reproduction linked in the issue and trace the focus changes when a dialog opens, especially when the first focusable element has an interestfor attribute. Review the interestfor, dialog, and focus behavior described by the issue. Done means automatic focus does not trigger an unintended interest notification, while normal interest behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100