Files
AndreaSlopFotografie/aidlc-docs/features/prerendering/construction/display-fallbacks/code/verification-log.md
T
SluijsensandClaude Opus 5.5 44125155bc Makes Reveal, deferred images and the first row work from the HTML
Reveal content is visible in the HTML and only content below the viewport hides
after hydration. Deferred photos get a noscript twin, and the first row of the
portfolio loads eagerly per column count. Some old tests still expect the former
behaviour; they are rewritten next, so this commit's test run is not fully green.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-31 22:57:05 +01:00

6.8 KiB

Verification log: display fallbacks (unit 2)

Status values: open (not yet settled), OK, BLOCKED, DEVIATION.

V-D# Point Step Outcome Evidence Status
V-D1 useLayoutEffect in Reveal during renderToString, hydrateRoot and StrictMode (double effect): no warning, no mismatch, the hide step runs once visibly. 2 No warning, no mismatch, hide step visible once. Unit test src/displayHydration.test.tsx (hydrate() under StrictMode, rectangles stubbed): no recoverable error, in-view Reveal stays visible, below-the-fold becomes hidden after hydration and visible after the fake observer fires; no console warning in the run. Browser probe on the built site (rAF sampling of getComputedStyle opacity from the first frame, 2.5 s; /over-mij, /soorten-fotoshoots, /portfolio at 412x823; /, /over-mij at 1350x940; / at 412x823): elements in view at the first sample (2, 2, 1, 0, 2, 0 of 5, 11, 3, 14, 5, 14) were 1 in every frame; elements below the fold (3, 9, 2, 14, 3, 14) ended hidden with opacity values only 0 or 1, never an intermediate value; no console error or warning. /soorten-fotoshoots: first frame with a 0 is frame 16 of 456 (the hide happens after hydration, no transition). reducedMotion reduce (/ and /over-mij at 412x823, /soorten-fotoshoots): every sample 1, nothing hidden. /portfolio grid wrapper at 412x823 now stays visible (the BR-RVL-13 defect). OK
V-D2 With JavaScript on, the twin image is never requested (request log on /soorten-fotoshoots and /portfolio before any scroll), and the preload scanner does not read inside noscript. Also that Emotion writes the shared class once (one <style> for the two images). 3 Twin never requested with JavaScript on; one Emotion class. Built dist, Chrome, 1350x940, JavaScript on. /soorten-fotoshoots: 12 image requests in total, 12 distinct URLs, none twice; 4 before load + 500 ms (both logos, newborn, newborn-detail: photos in or near view); set of requested URLs equals the set of currentSrc of the displayed img elements. /portfolio: 18 requests, 18 distinct, none twice, 8 before load + 500 ms (logos and 6 photos near the viewport), requested set equals the displayed set. No console message. Raw HTML: no preload link for a twin. Emotion: one style block data-emotion="css qvpj2z" (soorten) and one for css-1qa5q9y (portfolio tile class), shared by the deferred image and its twin. OK
V-D3 <noscript> inside <head> and inside the header and the panel hydrate without a mismatch in hydrateRoot(document) (the shell hydrates <html>), and the head hoisting of HeadContent keeps the CSS in the head. 3 (head, twin), 7 (header and panel) Head and twin part OK; header and panel part is settled in the menu step. Raw dist/client/soorten-fotoshoots.html and portfolio.html: the noscript with the style sits inside head (after HeadContent); document.head.querySelector("noscript") exists in the browser with the CSS as text; document.querySelectorAll("noscript").length equals the raw HTML count (10 on /soorten-fotoshoots, 17 on /portfolio). No hydration error or console message in the browser. JavaScript off: every displayed img has complete and naturalWidth > 0 (12 of 22 and 18 of 35 images displayed, matching the request counts), every img[data-deferred] is display none and has no src, noscript is display: contents; screenshots of both pages looked at, no broken-image box. OK (head, twin); header and panel open until the menu step
V-D4 Fragment navigation to a fixed element does not scroll in Firefox and Safari, and Chrome on Android (only desktop Chrome was probed). If one scrolls, the fixed header target moves to a zero-size fixed element. 18 (Chrome part) open
V-D5 The comparison of BR-DMS-05 (E against D on mobile, three runs each, same machine) and its report to the owner when E is below 0.9 or below D. 26 open
V-D6 Height of every Reveal at 320, 360, 412, 768, 1350 px wide against the limit of BR-RVL-13. 18 open
V-D7 After the gate measurement: whether loading="lazy" on the light logo and the contact portrait changes score and LCP as estimated; that the logo does not flash on / or on a client navigation from / to another page and back. 24, 25 open
V-D8 The raw-HTML e2e tests that count img or links (rawHtml.e2e.ts) with noscript content present. 20 open
V-D9 The visible focus ring of the two menu links in Chakra's reset (a bare a outside Chakra components). 17 open
V-D10 Whether Chrome really excludes the viewport-filling hero photo from LCP (so text is the candidate on /), by a trace. Only explains /; changes no rule. 25 (only if a trace exists) open
V-D11 The first React 19 upgrade: the hoisting facts of BR-PRE-01 (tested by BR-PRE-04). 15 open
V-D12 Visual check without JavaScript on every page at 390 and 1280 px (screenshots through E2E_SCREENSHOT_DIR, looked at, not compared): header, hero, nav, footer, empty areas left by hidden controls (mb of the filter bar, the gate's margin). 16 open
V-D13 <picture> with display: contents around the grid tile DeferredImage: the tile keeps its size, the hover zoom, the focus ring and the reading order; the <source> photo is requested once when src is set later; hydration is clean for tiles 2 and 3 (<picture> and noscript children). 4 (proof), 14 (test), 19 (e2e) Tile keeps size, zoom and focus; one request per photo; clean hydration in the browser. Boxes of all portfolio tiles before and after at 320x568, 412x823, 768x1024, 1023x768, 1024x768, 1350x940: identical to 0.01 px (baseline taken from the dist built after Steps 2 and 3, which change no box). Photo requests before the load event: 1 at 320, 390, 412 px; 2 at 768 and 1023; 3 at 1024 and 1350; each URL once, none for tiles 4 and up. After a scroll to the bottom each of the 10 grid photos was requested exactly once at every width. Distinct x positions in the first row: 1, 1, 1, 2, 2, 3, 3 at 320, 390, 412, 768, 1023, 1024, 1350 = column count. Hover and keyboard focus (Tab): tile image transform matrix(1.05 ...), zIndex 1, outline solid 2px on tile 2 at 768 and tiles 2 and 3 at 1350. dist/client/portfolio.html head: React preload for tile 1 (f41a1916, no media), f41a1922 with media (min-width: 48em), f41a7883 with media (min-width: 64em), no other photo preload. No hydration error or console message at any width (production build). OK
V-D14 Which tiles Chrome reports as the largest paint at 412, 768 and 1350 px after the change (the probe saw f41a1916 at 412, f41a1922 at 768 and f41a7883 at 1350 without the eager row), and that these are first-row tiles. 25 open
V-D15 /portfolio?shoot=gezin: the preloads of unfiltered tiles 2 and 3 and the remounted first row of the filtered list do not fetch the same photo twice. 19 open