Repository navigation
Model live user-validity selector state - #572
Merged
Merged
Conversation
This was referenced 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.
Closes #571. Advances #257 and #235.
Adds non-reflected user-interaction validity state and live
:user-valid/:user-invalidmatching. Native/semantic edits mark the state; programmatic/default writes do not; reset clears it while reparent/detach preserve it. A dedicated dependency reuses the existing value transition and recascades only the subject without adding structural invalidation.Remaining constraint-validation families and form aggregation stay on #257.
Validation:
git diff --checkonly under the current implementation-first direction. Authored WPT-derived/native contracts and runtime/performance/package gates remain unexecuted.