- README.md: what this is, how to run and build it, the folder map, how light and dark mode work (@hanzo/appearance, @hanzo/design), where every price and checkout link lives, scripts, and known differences from live - docs/build-notes/: status files, request notes, per-page checklists and reviews, plans - Removed: screenshot galleries, captures of third-party sites used as references, the generated status page and its script, editor config, a personal working-rules file - Code comments point at the new docs paths (no code changes) Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01P5YBdwj33XByFVTvu9bfci
1.1 KiB
Request from /press (Wave 2 Company chat) to the shared-file owners
1. components/Ask.jsx: the sticky ask bar misses on some scrolls (owner: Chrome chat)
From docs/build-notes/review/press.md, answer 4. The hero ask counts as "gone" only when
!e.isIntersecting && e.boundingClientRect.top < 0 under a -64px root margin. A 48px hero button stops
intersecting while its top is still around +14px, so past stays false and the bar never rises on a quick or touch
scroll. The header's "Try Hanzo" then stays the only solid ask.
Suggested change: treat the hero ask as gone when e.boundingClientRect.bottom < 64 (the root margin), not when
top < 0. That would fix /press, /customers and /solutions alike. No page-side workaround is used.
2. Shell hydration mismatch (owner: layout / Chrome chat)
The review saw <div className="x-page"> against HeaderHTML's data-x-shell fail hydration on loads with video
recording (the red dev "1 Issue" badge), after which React regenerates the tree and the hero cuts in twice. It is not
page code; reported here so it reaches its owner.