Tabster should include a way to indicate that it was the cause of programmatic focus about tabster HOT 6 OPEN

This should already be possible https://github.com/microsoft/keyborg/blob/bdfc82f67b743c64e8d9ec0bfac50b75d72e9cef/src/FocusEvent.ts#L252-L259

from tabster.

@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?

from tabster.

Ah @khmakoto I see what you mean. Can you please describe the scenario where this would be needed?

from tabster.

It's for scenarios like the one in Tooltip here, where we do not want a tooltip to show if things like closing another surface would cause focus to be restored to a trigger button with a Tooltip attached to it. However, there are products that have a mixture of tabster usage + their own custom solutions for certain focus related scenarios where they sometimes move focus programmatically and would like the Tooltip to show up in those scenarios. which is impossible now because there is no way to differentiate between those.

https://github.com/microsoft/fluentui/blob/master/packages/react-components/react-tooltip/src/components/Tooltip/useTooltip.tsx#L179-L199

from tabster.

Tabster dispatches tabster:movefocus event every time before it moves focus. See TabsterMoveFocusEventDetail for the event's detail signature (it has next element and related keyboard event, if any). You can also can call preventDefault() and Tabster won't handle it at all (but you will have all the data about what it wanted to focus).

from tabster.

Tabster also adds typings for addEventListener() so that you don't need to import the event signature directly, it will be inferred automatically when you do document.addEventListener('tabster:movefocus', e => ...).

from tabster.