Fix component interactions and design math boundaries - #3
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The shared kit could miscalculate wrapping text, accept invalid numerical inputs, lose optional-hyphen word content, and mishandle required fields or keyboard focus. This change fixes the mathematical contracts and component interactions, with reproductions for each repaired defect.
Required custom selections now participate in native form validation without duplicate accessible controls or payload fields. Keyboard navigation, controlled overlay focus, asynchronous project snapshots, and component timers retain their expected behavior. Responsive token expressions and strict CLI results preserve the actual artifact evidence.
Validation: local pre-commit lint and strict types passed; all 941 unit tests passed. The focused audit also passed the required-form Chromium harness and built CLI smoke checks. The private workbench exercised the packed packages through 49 browser workflows and all four preset matrices (180/180 each). Remaining browser and accessibility coverage is recorded in the workbench audit.
The release gate now pins the exact repaired mathematical evidence: 180/180 project fixtures and 720/720 matrix fixtures. Five direct regression tests pass after failing against the obsolete policy; the original 17/45 failure baseline is preserved as historical evidence. Unexpected failures, changed layouts, incomplete coverage, and inconsistent strict exit statuses remain rejected.
The packed SvelteKit starter also passes both real browser cases and its server validation checks. Empty native-required fields block create requests, focus the invalid field, and retain drafts; valid create/update/theme flows and the no-JavaScript path remain covered.
Package versions are unchanged; this PR does not request an npm publication.