Files

3.1 KiB
Raw Permalink Blame History

/integrations: shared changes requested (Wave 2 Proof chat)

  1. 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).
  2. components/Morph.jsx (shared): inside document.startViewTransition(...) the update callback resolves through requestAnimationFrame(() => 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, setTimeout 81 ms. Fix: setTimeout(ok, 16) in place of requestAnimationFrame(() => ok()). With that change simulated, /integrations cards land in their guide's h1 (docs/gallery/integrations/click-through.jpg).
  3. components/v2/SceneWipe.jsx and components/v2/MaskLines.jsx (shared): both read useReducedMotion() 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;). /integrations uses page-local copies with that fix (components/pages/integrations/Wipe.jsx, Mask.jsx) until the shared files change.
  4. Header ask on phones (shared components/Ask.jsx / header) (review fix 3): on /integrations and 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.
  5. 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.
  6. public/hanzo.css sets scroll-behavior: smooth on html (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). /integrations and the guides work around it page-locally (landAtTop in components/pages/integrations/intParts.jsx sets scroll-behavior: auto for the page change only). A site-wide fix: html { scroll-behavior: auto } in globals, or the same switch in components/Chrome.jsx around its route-change scrollTo(0, 0).
  7. 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.
  8. 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.