fix(ui): preserve consumer and native interaction behavior - #292
Merged
Merged
Conversation
pathscale
force-pushed
the
fix/icon-doc-selector-warning
branch
from
September 12, 2026 04:23
ea3f3ac to
b3857af
Compare
pathscale
force-pushed
the
fix/icon-doc-selector-warning
branch
from
September 12, 2026 04:28
b3857af to
6c9f65d
Compare
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.
UI 3.2 had consumer-visible interaction regressions, incomplete native coverage, and compound controls whose authored identity did not consistently reach the semantic control. A repeated component could therefore be hard to address reliably even when its caller supplied a stable row key.
This branch preserves the Icon documentation warning fix and rapid ImmersiveLanding navigation fix, then corrects the behavior found by consumer testing:
Every UI component now accepts a caller-owned
id. Compound components derive their triggers, fields, popovers, calendars, menu items, pagination buttons, and other semantic controls from that base. Repeated children use stable data keys such as ISO dates, menu keys, page numbers, preset values, and saved-theme identities. The public contract tells callers to derive a repeated component's base from the item's stable key.The package exports a canonical 101-family component inventory. The UI native registry and js.software compare against it at build time, and the contract check requires every public family in the Solid Layouts consumer manifest. FlexGrid is included and its incremental reveal is exercised natively.
Local release evidence:
The reviewed tarball has SHA-256
230c2d6bf3e314667066e46b5eff7606b308eca20ef893ae9a44b39b488a6e8a. The release workflow will calculate the patch version after owner review and merge. This PR itself does not publish or deploy.