← Commit history

Unstick last-resort upgraded to a REAL input click (proven cure). The stuck-occlusion state (window frontmost, page reports hidden, Chrome paints nothing) hit John TWICE today including on a freshly opened window, and both soft cures (CDP lifecycle active, ALT-nudge SetForegroundWindow) failed live while a genuine mouse click fixed it instantly both times. The auto-unstick now escalates: lifecycle, forced activation, then a real desktop_click on the window's empty tab-strip area via AD (pure activation, cannot hit page content; only runs when the user is already looking at the frozen window).

John Lauer ·e0cbfeb691 ·3mo ago ·parent 48226bc
4 files changed +25−6
adom-bridge-puppeteer-manifest.json+4−4
@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.9.182",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.182/adom-bridge-puppeteer-v1.9.182.zip",-  "sha256": "a005455f0dcaf4003aa975b8a7cba5dbfcdfbe943e4175dede56808da8cf671c",-  "size": 419485,+  "version": "1.9.183",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.183/adom-bridge-puppeteer-v1.9.183.zip",+  "sha256": "3ef8cf40e2f62af1d7525c14aeba9ba6d2734916984925a6ce47ad308ec67b97",+  "size": 419914,   "verbPrefixes": [     "browser_",     "desktop_recorder_",
src/BRIDGE_VERSION+1−1
@@ -1 +1 @@-1.9.182+1.9.183
src/bridge.json+1−1
@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "1.9.182",+  "version": "1.9.183",   "description": "Drives a browser ALREADY on the machine \u2014 installed Chrome, else Microsoft Edge (every Windows PC ships with Edge) \u2014 launched with a FRESH isolated profile, so the common case has NO ~150 MB Chrome-for-Testing download and it never touches the user's real tabs/logins. Binds its local server to LOOPBACK (127.0.0.1) only, so no Windows Firewall 'allow Node through the firewall' prompt ever pops. Chrome for Testing is fetched only as a LAST RESORT if the machine has no Chromium browser at all. SPAWN-VERIFIED fallback: pup tries each detected browser (Chrome \u2192 Edge \u2192 CfT) and actually launches it, falling through to the next if one won't start (and handling browsers like Edge that relaunch onto another PID), so a corrupt/partial install never hard-fails an open. The browser that launches is cached as the default (persisted across restarts) so it isn't re-probed each time. On spawn the bridge SELF-WARMS: detects browsers + disk, and only if the box has no Chrome/Edge and no cached CfT does it background-fetch CfT so the first open is instant. browser_use pins a specific browser (chrome | edge | cft | auto); {browser:'chrome',install:true} downloads & installs REAL Google Chrome (user-scoped, no admin) on an Edge-only box. browser_readiness (READ-ONLY) reports which browser will be used + the full candidate list + the default + free disk. Every failure returns a specific errorCode + _hint (chrome_install_no_disk, chrome_download_network, chrome_install_permission, chrome_stable_not_detected, \u2026). Launches with FULL browser permissions by default for full debug (strictPermissions:true opts out). Headful automation: open/close windows+tabs, navigate, screenshot, eval JS, record. pup is a GENERIC, non-profile browser only \u2014 every session is a fresh isolated Chrome/Edge process, never the user's real signed-in browser; profile defaults to sessionId. To drive the user's REAL Chrome/Edge (their profile, cookies, SSO), use the Adom browser EXTENSION's nbrowser_* verbs \u2014 a separate bridge, not pup's job. macOS (v1.9.74+): full parity with mac-native mechanics \u2014 background-by-default is the app-level hide (windows stay drivable/screenshottable while hidden), raise/lower map to unhide+activate/hide, browser_alert_window posts a native toast whose click focuses the window, browser_use {browser:'chrome',install:true} installs Chrome from the official dmg, and taskbar identity/badging remains Windows-only.",   "homepage": "https://wiki.adom.inc/adom/adom-desktop",   "author": "Adom Inc.",
src/server.js+19
@@ -2363,6 +2363,25 @@ async function unstickIfHiddenWhileFront(sessionId, session, fgHwnd, hwnd) {     await new Promise(r => setTimeout(r, 900));     try { vis = await withTimeout(tab.page.evaluate('document.visibilityState'), 1500, 'vis-probe'); } catch (e) {}   }+  if (vis === 'hidden') {+    // v1.9.183: LAST RESORT that actually works — a REAL input click. Proven live twice on John's+    // Slides window: CDP lifecycle 'active' and the ALT-nudge SetForegroundWindow both left the page+    // hidden; a genuine mouse click on the window cleared it instantly both times (Chrome's stuck+    // occlusion only recomputes on real input). Click the EMPTY tab-strip area (right side, clear of+    // the window buttons): pure activation, cannot hit page content. Acceptable cursor blip: this+    // branch only runs when the user is ALREADY looking at this frozen window.+    try {+      const fw = adPayload(await chrome.adCommand('desktop_find_window', { titleContains: `(session: ${sessionId}` }, { timeoutMs: 5000 }));+      const r = fw && (fw.best || (fw.data && fw.data.best)); const rect = r && r.rect;+      if (rect && rect.width > 600) {+        const cx = Math.round(rect.left + rect.width - 300);+        const cy = Math.round(rect.top + 10);+        await chrome.adCommand('desktop_click', { x: cx, y: cy, reason: `unstick frame-frozen pup window "${sessionId}" (real activation click on empty tab strip)` }, { timeoutMs: 8000 });+        await new Promise(r2 => setTimeout(r2, 1200));+        try { vis = await withTimeout(tab.page.evaluate('document.visibilityState'), 1500, 'vis-probe'); } catch (e) {}+      }+    } catch (e) {}+  }   const fixed = vis !== 'hidden';   if (fixed) {     recordCleanup(`pup detected your "${sessionId}" window was front-and-center but Chrome had stopped painting it (stuck occlusion after a hang) — pup unstuck it automatically; scrolling and rendering work again.`);