Tooltip of dismiss button in Dialog control is not opened on tabbing through keyboard

[Harkesh030679]

Tooltip of cross button in Dialog control is not opened on tabbing through keyboard

Environment Information

OS: Win10
Browser: Chrome, Edge

Describe the issue:

Tooltip of cross button in Dialog control is not opened on tabbing through keyboard, Tooltip is opened on hover properly

Please provide a reproduction of the issue in a codepen:

Link
https://developer.microsoft.com/en-us/fluentui#/controls/web/dialog
Snap

Actual behavior:

Tooltip of cross button in Dialog control is not opened on tabbing through keyboard

Expected behavior:

Tooltip of cross button in Dialog control should be opened on tabbing through keyboard

Documentation describing expected behavior

[aneeshack4]

@Harkesh030679 You can wrap it in TooltipHost like in the examples here https://developer.microsoft.com/en-us/fluentui#/controls/web/tooltip

[aneeshack4]

Oops my bad - there's actually no custom renderer available. @ecraig12345 has more details on this.

[ecraig12345]

At this point it's expected that the tooltip won't open on keyboard focus of the dismiss button because we're using only the browser's native tooltip (title property), which doesn't work that way. @aneeshack4 is right that we could add a tooltip that opens on keyboard focus by wrapping the button in a TooltipHost, but this isn't something we'd want to add by default due to bundle size concerns.

We could however consider adding a custom renderer onRenderDismissButton which would let you wrap with the button with a TooltipHost yourself. I've marked this as a feature for backlog review (if we do this it should also be added to Panel and other controls with dismiss buttons), though we may not get to it for awhile since we're currently focused on larger work items around performance and coherence. It's also possible we may want to defer this until a later version where we have slots available instead of custom render functions.

[msft-fluent-ui-bot]

Because this issue has not had activity for over 150 days, we're automatically closing it for house-keeping purposes.

Still require assistance? Please, create a new issue with up-to date details.