Allow kebab-case indexing on CSSStyleDeclaration - #64340
Draft
Ryan Cavanaugh (RyanCavanaugh) with Copilot wants to merge 2 commits into
Draft
Ryan Cavanaugh (RyanCavanaugh) with Copilot wants to merge 2 commits into
Ryan Cavanaugh (RyanCavanaugh) with Copilot wants to merge 2 commits into
Conversation
typescript-automation
Bot
added
the
For Milestone Bug
Copilot started work on behalf of
Ryan Cavanaugh (RyanCavanaugh)
September 19, 2026 02:10
View session
Co-authored-by: RyanCavanaugh <6685088+RyanCavanaugh@users.noreply.github.com>
typescript-automation
Bot
added
For Uncommitted Bug
Copilot
AI
changed the title
[WIP] Fix error accessing CSS property value using kebab case
Allow kebab-case indexing on CSSStyleDeclaration
Sep 19, 2026
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
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.
CSSStyleDeclarationsupports accessing CSS properties via dashed/kebab-case names at runtime (e.g.style['background-color']), but the type only declared a numeric index signature plus camelCase named properties. This caused TS7015 ("implicitly has an 'any' type") under--noImplicitAny:Changes
[index: string]: anytoCSSStyleDeclarationBaseinlib.dom.d.ts.string-typed index signature wasn't viable: methods likegetPropertyPriority(property: string): stringhave a function type incompatible with astringindex signature, and this conflict propagates to the mergedCSSStyleDeclaration/CSSStylePropertiestype.anyavoids that conflict (compatible with any property type) while resolving string-keyed access without an implicit-any error. Existing named properties and methods keep their specific declared types; only unrecognized string keys fall back toany.cssStyleDeclarationKebabCaseIndex.ts) covering read/write access via kebab-case property names under--noImplicitAny.CSSStyleDeclarationobject #59968