mirror of
https://github.com/hanzoai/site.git
synced 2026-11-20 21:21:13 +00:00
Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01P5YBdwj33XByFVTvu9bfci
3.1 KiB
3.1 KiB
/integrations: shared changes requested (Wave 2 Proof chat)
- UI strings for
content/ui-strings.json(the register is shared; the page uses these today, pending James):int_find: "Find your tool" — the catalogue search field's placeholder and accessible name (the page's Beyond).int_no_match: "Nothing matches" — the empty state when the search finds no tool (followed by the query in quotes).
components/Morph.jsx(shared): insidedocument.startViewTransition(...)the update callback resolves throughrequestAnimationFrame(() => ok()). Chromium suppresses rendering, and so rAF, during that callback, so it only resolves at the 4 s View Transition timeout: every in-site click freezes about 4 s and the morph is skipped. Measured: rAF inside the callback 4,069 ms,setTimeout81 ms. Fix:setTimeout(ok, 16)in place ofrequestAnimationFrame(() => ok()). With that change simulated,/integrationscards land in their guide's h1 (docs/gallery/integrations/click-through.jpg).components/v2/SceneWipe.jsxandcomponents/v2/MaskLines.jsx(shared): both readuseReducedMotion()during the first render, so with reduced motion on the client's first render differs from the server HTML (a hydration mismatch: the red "1 Issue" badge and a console error). Fix: read it after mount (const [m, setM] = useState(false); useEffect(() => setM(true), []); const reduce = m && rm;)./integrationsuses page-local copies with that fix (components/pages/integrations/Wipe.jsx,Mask.jsx) until the shared files change.- Header ask on phones (shared
components/Ask.jsx/ header) (review fix 3): on/integrationsand every/integrations/*guide the phone header keeps a solid "Try Hanzo" for the whole page, so the first 375×812 screen has two solid fills with two labels. Wanted: the page's own ask label ("Get an API key" / "Get API key — Free"), quiet (outline) while the hero ask is on screen, solid only after it leaves, as desktop already does. Also: the header ask's crossfade never passes through a flat mid-grey. - Header glass over dark rooms (shared header) (review fix 10): over the code block and the black room the header should be clean glass or a dark header, not a grey band with white end caps.
public/hanzo.csssetsscroll-behavior: smoothonhtml(Hanzo's own stylesheet; Lenis overrides it only on fine pointers). On a phone every in-site link therefore shows the new page at the old offset and glides it up (~500 ms)./integrationsand the guides work around it page-locally (landAtTopincomponents/pages/integrations/intParts.jsxsetsscroll-behavior: autofor the page change only). A site-wide fix:html { scroll-behavior: auto }in globals, or the same switch incomponents/Chrome.jsxaround its route-changescrollTo(0, 0).- Cookie card (shared) (family review fix 4): at 1470×801 it should not intersect the hero code or route diagram; at 375×812 it should be 160px tall or less.
- FamNext card-to-page transition (shared engine) (family review fix 6): hold 700 ms or less; the flying title should land within 12px of the destination h1.