browser-renderlisted

# Browser Render (flash-free HTML → image) When you need to render a local HTML/SVG file to a PNG or PDF to inspect it (e.g. checking how a generated page, character sheet, or report looks), do NOT launch Chrome with `--headless=new`. On macOS that mode spins up a real GPU/window surface and produces a visible **white screen flash** on every launch. In a tight render→check→fix loop that strobes the whole display every few seconds and reads, to the user, like something is repeatedly taking a screenshot. (This was the cause of a real "my screen keeps flashing" report on 2026-06-03 -- a render loop on the D&D character sheet.) Important: the flash is purely cosmetic -- headless Chrome screenshots a **file**, never the user's actual screen, so there is no privacy/capture concern. But it is alarming and unnecessary. Use a flash-free path. ## Preferred: `--headless=old` One-flag change. The legacy headless mode renders fully offscreen (no window surface, no flash): ```bash CHROME="/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" "$CHROME" --headless=old --disable-gpu --no-first-run \ --user-data-dir=/tmp/render-$$ --hide-scrollbars \ --window-size=1000,1400 --screenshot=/tmp/out.png \ "file:///tmp/page.html" ``` Verified to still produce a PNG on Chrome 148 (2026-06-03), even though old headless was nominally removed around Chrome 132 -- the flag is still honored. **Caveat:** confirmed it *renders*; the no-flash behavior was not visually self-verified (can'