Skip to content

refactor: Keyboard focus ring controller #1684

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

rkaraivanov
Copy link
Member

No description provided.

Comment on lines +12 to +14
'keyup',
'focusout',
'pointerdown',
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was going to note that pointerdown is not exactly the same as click in terms of user interaction, though that behavior is entirely defined by us (browser's native focus-visible seems to clear on blur only), so it's prob fine.
Speaking of blur, that's also not quite the same since focusout bubbles, right? How safe is that change - I saw the carousel addition to prevent it, but could some internal content (user content/tempaltes) mess with the handler?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like the only possible issue is with carousel that already used focusout instead of blur like the buttons for example, so it might be a non-issue. Still, only trying to figure out if that can creep on us in the future

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants