Skip to content

fix(runtime): preserve empty union attributes in custom elements (#6963) - #6968

Open
Elements2720 wants to merge 1 commit into
stenciljs:mainfrom
Elements2720:fix/custom-elements-empty-union-attr
Open

Elements2720 wants to merge 1 commit into
stenciljs:mainfrom
Elements2720:fix/custom-elements-empty-union-attr

Conversation

@Elements2720

Copy link
Copy Markdown

Summary

attributeChangedCallback now treats only strict equality and nullish pairs as unchanged, so an empty string remains distinct from false for boolean|string props. Added a dist-custom-elements browser regression test.

Evidence

  • Before: focused Wdio spec failed with Expected empty string and Received false.
  • After: focused Wdio spec passed in Chrome 155 (1 passing); full Jest passed (252 suites, 4172 tests, 22 snapshots).

Merge Danger

Door: two-way

Blast Radius: runtime

Fixes #6963

@Elements2720
Elements2720 requested a review from a team as a code owner October 20, 2026 01:24

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: empty attribute is ignored on a boolean | string prop in dist-custom-elements (regression in 4.38.0)

1 participant