Repository navigation
feat(landing): state-motion polish (hover, press, lightbox, theme icon) - #154
Merged
Merged
Conversation
Audit of issue #63 against motion principles. The landing was already sober (no pulsing, no blur-everything, no stagger spam; reveal and counters respect prefers-reduced-motion), so the fixes are motion gaps rather than new decoration: - Hover/focus transitions (160ms) on buttons, links, feature rows and table rows: those states changed instantly today. - Press feedback: scale(0.97) on :active for actionable elements. - Lightbox enters with a 180ms fade plus a subtle image scale; closing stays instant (getting out is more urgent than getting in). - Theme icon micro-rotation on user click only, never on initial load. - Slider keeps its instant swap on purpose (screenshot browsing is data-like and arrow-driven). - Everything new is disabled under prefers-reduced-motion. No featrow stagger: rejected as motion for its own sake.
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 #63.
Audit result: the landing was already sober - no pulsing indicators, no blur-everything entrances, no stagger spam, and the existing reveal/counter system respects prefers-reduced-motion. The real findings were motion gaps (state changes that happen with zero transition), not missing decoration:
All new motion is disabled under prefers-reduced-motion. Verified with Playwright 12/12 on a local static server: computed transitions, lightbox animation, theme swap class, reveal/slider intact, zero console errors, and the reduce-motion context reports transitions/animations off.