fix: make landing scroll-reveals trigger earlier and finish faster#173
Merged
Conversation
Sections sat invisible while scrolling because reveals waited for deep viewport intersection and ran long animations: - LandingPage .rh-rv: observe at 6% visibility (was 15% + -8% rootMargin), transition 0.45s/12px (was 0.6s/16px), stagger delays tightened - RayVerifySection: framer-motion viewport amounts 0.2-0.3 (was 0.4-0.6), durations 0.4-0.5s (was 0.5-0.7s), per-stage stagger 0.07s (was 0.12s) Worst case was the dark RayVerify band: pipeline stages needed 60% visibility plus ~1.7s of staggered animation, reading as an empty box.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| const io = new IntersectionObserver( | ||
| (entries) => entries.forEach((e) => { if (e.isIntersecting) { e.target.classList.add('in'); io.unobserve(e.target); } }), | ||
| { threshold: 0.15, rootMargin: '0px 0px -8% 0px' }, | ||
| { threshold: 0.06, rootMargin: '0px 0px 0px 0px' }, |
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
2 participants
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.
Summary
The homepage's scroll-reveal animations triggered too late and ran too slow, so whole sections sat blank while scrolling — worst in the dark RayVerify band, where pipeline stages required 60% viewport visibility plus ~1.7s of staggered animation and read as an empty box. Pricing's third card, role cards, and the trust grid had the same lag in milder form.
Changes
.rh-rvreveals): IntersectionObserver now fires at 6% visibility with no negative rootMargin (was 15% +-8%); transition shortened to 0.45s / 12px rise (was 0.6s / 16px); role/pricing stagger delays tightened to 0.05s steps (was 0.07s).amountlowered to 0.2–0.3 (was 0.4–0.6); durations 0.4–0.5s (was 0.5–0.7s); per-stage stagger 0.07s (was 0.12s); smaller entry offsets.Animation-timing only — no copy, layout, or design-system changes.
prefers-reduced-motionpaths untouched.Test plan
tsc --noEmitcleanvite buildgreenvite previewwalkthrough: all three pricing tiers, trust grid, timeline, ROI, and RayVerify pipeline now reveal promptly at normal scroll speed