[KeyCode, AnchorRegion, Popover] Add key navigation in AnchorRegion / Popup #1800
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[KeyCode, AnchorRegion, Popover] Add key navigation in AnchorRegion / Popup
1. FluentKeyCode
FluentKeyCode
component to unregister thekeydown
event when the component is deleted.2. FluentAnchorRegion
AutoFocus
attribute to set whether this region should receive the focus when the component is loaded.FocusToNextElementAsync
andFocusToOriginalElementAsync
methods to move the focus to thenext element included in this anchor region only and to the initial element that triggered the anchor region.
3. FluentPopover
Adding
AutoFocus
attribute to set whether the element should receive the focus when the component is loaded.If this is the case, the user cannot navigate to other elements of the page while the Popup is open.
Default is true.
Adding
CloseKeys
attribute to set the keys that can be used to close the popover (ESC).Demo (using only keyboard)