Restore routing and the UI showcase interactions - #55
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
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 UI showcase had several production-visible regressions: Chrome route transitions could tear down the Solid effect incorrectly, global search reloaded or remained over the next page, the theme builder had drifted from AgencyZero's composition controls, glass and depth controls did not reliably affect the preview, and the site still consumed UI 3.2.1.
This restores one persistent router-owned layout, adds in-place desktop/mobile search over every registered route, rebuilds the theme composer with the full colour flower and separate control/art accents, delegates glass curves to
@pathscale/ui3.2.2, restores random/reset/persistence/export behavior, and makes the showcase responsive. CSS export now escapes arbitrary theme names and only reports copy success after the clipboard write resolves. The production policy gate rejects Google Fonts and CSP policies that block UI's dynamic styles.Validation performed locally before push:
ps-qa0.7.2 + rebuiltchuzz-headless: 669/669 checks across all 13 groupsOcean "Night" \\ reef): exported selector parses and matches the exact name; clipboard bytes exactly match the generated CSSbun run buildandbun run typecheckbun run qa:production-policyNo deployment or merge is included.