The current solution assumes that the component that triggers the CallOut is always a button. The button is not always a preferred component that triggers it because the Windows Narrator reads it as Button and the user might expect more than a help CallOut. This pull request adds the keyboard handler to the component that triggers irrespective of the type of the component.
Jahnp
commented
6 years ago
The current solution assumes that the component that triggers the CallOut is always a button. The button is not always a preferred component that triggers it because the Windows Narrator reads it as Button and the user might expect more than a help CallOut. This pull request adds the keyboard handler to the component that triggers irrespective of the type of the component.