Files
pipelines/app/notes/artifact-browser-interaction-20261105.md
T

27 lines
1.6 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Artifact browser interaction verification — 2026-11-05
Verified existing HTML artifact behavior in an isolated Chrome fixture built
from the warning-display branch, using `tool/capture/`. No production chat/run
was changed and no artifact-viewer source changes were needed.
At 1100×900: opened run 7 → Artifacts → release-dashboard.html, entered Full
screen, scrolled to Section 8 and the bottom heading, returned to the top, then
panned horizontally to the table's RIGHT EDGE column. Inspected all PNGs under
`/private/tmp/artifact-fullscreen-check/` (inline, fullscreen, bottom, right edge).
At 560×1000: entered Full screen, clicked Zoom in, asserted the sandboxed frame
has a scale transform, clicked Actual size, asserted that transform is reset,
and exited fullscreen. Inspected all PNGs under
`/private/tmp/artifact-zoom-check/`. Both capture scripts completed and cleaned up
their browser/server processes. The listing capture in
`/private/tmp/artifact-interaction-check/` was also inspected.
This proves desktop Chrome wheel scrolling/panning and the viewer's zoom
controls, including a narrow viewport. It does not prove physical touch/pinch,
Safari link/clipboard policy, or native-device behavior. Web artifact zoom uses
the existing buttons: the sandboxed document does not receive native pinch zoom.
No Android devices were attached (`adb devices -l` returned an empty list).
A real Safari fixture rendered, but further native automation failed with
`cgWindowNotFound`; Safari interaction acceptance remains unverified. The owned
loopback fixture server was terminated and awaited; no personal Fold was used.