verifyfirst

preflight · 8 checks

I checked that a page renders correctly

A screenshot, headless capture or visual review was used to judge a page.

Before you call it done

  1. Confirm the animation loop runs at all before judging any frame.let n=0; requestAnimationFrame(()=>n++); setTimeout(()=>console.log('rAF fired:', n), 1000)guards against NS-001
  2. Capture console errors. Inert and wrong look identical in an image.Collect page errors during load; an element that never initialised renders nothing.guards against NS-002 NS-010
  3. Check the fonts you designed against actually loaded.document.fonts.check('1em "Family Name"')guards against NS-004
  4. Compare element count against visible count.document.querySelectorAll('.reveal').length vs those with computed opacity above zeroguards against NS-010 NS-030
  5. Confirm the capture used your device scale, colour scheme and stylesheet.devicePixelRatio, matchMedia('(prefers-color-scheme: dark)').matches, and print vs screen mediaguards against NS-049 NS-050 NS-051
  6. Wait for data, not for the load event.The load event fires before fetched content arrives; assert on the rendered rows.guards against NS-052 NS-009
  7. Compare a viewport capture against a full-page one before trusting either.A full-page capture flattens fixed elements and can skip content-visibility sections.guards against NS-074 NS-071
  8. Check for frames that resolved but were refused.performance.getEntriesByType('resource') — a refused frame has transferSize 0guards against NS-072

Plain text: /recipes.txt · all tasks