-
Notifications
You must be signed in to change notification settings - Fork 37
Tabster should include a way to indicate that it was the cause of programmatic focus #384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This should already be possible https://github.com/microsoft/keyborg/blob/bdfc82f67b743c64e8d9ec0bfac50b75d72e9cef/src/FocusEvent.ts#L252-L259 |
@ling1726 I know that you can check if something was programmatically focused or not, but I don't think you can check whether tabster was the cause of the focus moving programmatically or if something else was the cause, can you? |
Ah @khmakoto I see what you mean. Can you please describe the scenario where this would be needed? |
It's for scenarios like the one in |
Tabster dispatches |
Tabster also adds typings for |
When focus has been moved programmatically because of
Tabster
(say to restore focus to a trigger element after dismissing a popover or dialog), there should be a way to indicate that tabster was the cause of this programmatic focus (maybe through the keyborg event).The text was updated successfully, but these errors were encountered: