Closed bug report

Background screenshot shows a different document than the same session DOM and tab metadata

John Lauer · 2mo ago ·closed by John Lauer

On Windows AdomLapper, pup-bridge 2.0.458, background-only calls with explicit target AdomLapper and AI thread TMF8829 Depth Lab produced a DOM/capture mismatch. Related ownership/recovery history: #79 and #41, but this report does not establish the same root cause.

pup_list_windows initially returned count 0. An explicit pup_open_window for TMF8829-Depth-Lab with the skill-pack URL reported an existing window and new tab-2. pup_eval identified the Adom Wiki Skill Pack and found the newly published section. The subsequent pup_screenshot for the same explicit session returned an image of TPS389001DSER with an older LOD preview and many tabs. The screenshot does not show the document that was evaluated.

A later list_windows reported that same session at HWND 49613454 with only 2 tabs, active tab-2, title Adom Wiki Skill Pack and its URL; the screenshot visibly shows many component tabs. No foreground was requested. I stopped using this capture as publication evidence and did not kill/reclaim other windows.

Expected: DOM evaluation, selected tab, HWND capture and session identity agree, or the bridge fails with an actionable identity-mismatch hint. Verify HWND ownership against the actual selected browser target before capture, and include selected target URL/tab/window metadata with the image.

Relevant exact calls:

pup_open_window {"sessionId":"TMF8829-Depth-Lab","url":"https://wiki.adom.inc/adom/adom-wiki-skillpack","wikiView":"authed","foreground":false,"width":1440,"height":1000}
pup_screenshot {"sessionId":"TMF8829-Depth-Lab"}

The attached image is the returned screenshot. It is failed verification evidence, not the intended updated skill-pack render.

wiki-lod-contract-live

1 Reply

John Lauer · 1mo ago

Addressed in pup 2.0.649 (insiders). Every pup_screenshot response now carries captured {url, title, tabId, windowId, hwnd, via}, so an image can be checked against the DOM it claims to show. The extension lane and the CDP tab path capture by tab, which cannot cross windows. The one path that could, the OS window capture by hwnd, now reads the OS window title first and refuses with capture_identity_mismatch (both titles in the error) when it does not contain the tab's title. The original mismatch was on 2.0.458, before windows were bound by a birth token (2.0.630) and the geometry-based binding was deleted; it does not reproduce on 2.0.649 (measured: captured metadata matches the evaluated tab). Reopen with the captured block if a screenshot ever disagrees with its own metadata again.

John Lauer closed this · 1mo ago

Log in to reply.