refactor: update tabIndex logic to match standard HTML property #10543
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
web-padawan
commented
Nov 25, 2025
| * Indicates whether the element can be focused and where it participates in sequential keyboard navigation. | ||
| */ | ||
| tabindex: number | null | undefined; | ||
| tabIndex: number; |
Member
Author
There was a problem hiding this comment.
This change is needed to avoid conflicting with standard HTML which uses number.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
The usage of
tabindexwas necessary with Polymer: back in the day,tabIndexwould be converted totab-indexattribute and there was no way to configure this. With Lit, we can useattribute: 'tabindex'instead.Type of change