BREAKING: remove "tabIndex" assigned to handle by default #212
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.
Breaking change
This is a breaking change, so if you got here after debugging an issue with focus on the handle and just want to fix your issue quickly, just know that you should now pass
tabIndex={0}
to your handle element to make it focusable.More context
This change removes the default
tabIndex=0
attribute from the set that is being passed to the handle after an update.This means that by default the handle will not be set focusable and you have to manually add
tabIndex={0}
prop to your handle element.This change was introduced after the conclusion internally that maybe not every use case requires the handle to be focusable right away and this feature should be controlled from the user, which was not possible before. Since this is still major version 0 and pretty much still in active development, any API changes like this should be expected.