From 8a409e2d0ace73bb5761207d37b7201f2de2dc3d Mon Sep 17 00:00:00 2001 From: Alan Silva Date: Sun, 8 Nov 2026 00:15:40 +0000 Subject: [PATCH] Record repainted startup update browser evidence --- app/notes/startup-update-check.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/app/notes/startup-update-check.md b/app/notes/startup-update-check.md index 49825e87..e7ff36ab 100644 --- a/app/notes/startup-update-check.md +++ b/app/notes/startup-update-check.md @@ -36,8 +36,10 @@ The full-app fake-gateway web fixture was built with `PIPELINES_WEB_BUILD_ID=web-fixture-current` and served a same-origin `release.json` naming `web-fixture-new`. Browser interaction verified Material Later dismissal and Cupertino Refresh actually reloads the document (a JS -sentinel was cleared). Captures under `/tmp/review/startup-update-material-steady` -and `/tmp/review/startup-update-cupertino-final` were inspected. Fixture appearance +sentinel was cleared). Captures under `/tmp/review/startup-update-material-repaint` +and `/tmp/review/startup-update-cupertino-final` were inspected. Material required a one-pixel viewport resize and restoration +to force software Chrome to include unchanged canvas layers in the initial PNG. +The repainted capture shows the full dialog and intact shell. Fixture appearance uses a URL-only parameter, so the refreshed fixture returns to its default host; production appearance settings are unchanged. The static fixture intentionally keeps serving the old compiled build, so its update prompt recurs after reload.