← Commit history

The 'NOT foregrounded by Adom' caption is OFF by default now (John reasoned it out: 'i alt+tab to your pup windows too... this feature is very likely not possible to correctly track my moves'). He is right on two counts: (1) input-timing is only a heuristic for 'did the user raise this window' - a click, alt+tab, or window-click are all recent input, but the 2.5s watch tick vs the 1.5s idle window means a late tick would wrongly caption his own action; (2) more fundamentally, Windows blocks background processes from stealing the foreground, so the JS/Chrome self-raise the feature exists to catch rarely reaches the foreground at all - meaning it mostly fired on HIS actions and seldom on real ones. So the honest default is off. Kept as an opt-in toggle (idle-gate retained for anyone who enables it); a non-chosen stored 'on' migrates to off.

John Lauer ·3a538649dd ·3mo ago ·parent e3456f9
4 files changed +12−7
adom-bridge-puppeteer-manifest.json+4−4
@@ -1,10 +1,10 @@ {   "manifest_version": 1,   "name": "puppeteer",-  "version": "1.9.292",-  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.292/adom-bridge-puppeteer-v1.9.292.zip",-  "sha256": "7ba8083aa2fec0b26e4472105ba921868474ba2af6e0ea13409a6e6b538dba6d",-  "size": 719508,+  "version": "1.9.293",+  "url": "https://wiki.adom.inc/download/adom/adom-desktop-puppeteer-bridge/1.9.293/adom-bridge-puppeteer-v1.9.293.zip",+  "sha256": "85eedf47bb3ec3233fd50a0a8f5815d724d4ecdc23f4217c3aa4031c155201d6",+  "size": 719675,   "verbPrefixes": [     "browser_",     "desktop_recorder_",
src/BRIDGE_VERSION+1−1
@@ -1 +1 @@-1.9.292+1.9.293
src/bridge.json+1−1
@@ -2,7 +2,7 @@   "manifest_version": 1,   "name": "puppeteer",   "displayName": "Puppeteer (Chrome for Testing + Native)",-  "version": "1.9.292",+  "version": "1.9.293",   "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+6−1
@@ -2799,7 +2799,12 @@ function pupSettings() {   D.autoLogin = 'on'; D.reportIssues = 'on'; D.agentActivity = 'on';   // v1.9.275 (John: 'shouldn't there be a setting for whether to show the full jump list or not?')   D.jlViewTasks = 'on'; D.jlCloseAll = 'on';-  D.notMineCaption = 'on';   // v1.9.282 (John): the 'NOT foregrounded by Adom' caption, default on+  // v1.9.293 (John): the 'NOT foregrounded by Adom' caption is now OFF by default. He is right that+  // input-timing cannot reliably tell his own raises (click / alt+tab / window click) from a rare+  // JS raise - and Windows blocks most background foreground-steals anyway, so the case it exists+  // for seldom happens. Kept as an OFF-by-default opt-in; the idle-gate stays for anyone who turns it on.+  D.notMineCaption = 'off';+  if (_pupSettings.notMineCaption === 'on' && !(_pupSettings._chosen || {}).notMineCaption) _pupSettings.notMineCaption = 'off';   D.ownerChip = 'on';        // v1.9.284 (John): the floating owner-thread/profile chip, default on   // v1.9.286 (John: "i dont like seeing the title mangled anymore"): BOTH title decorations OFF by   // default. titleTag = the "(ai-thread: X)" resolution suffix (pup resolves transiently while the