cbrowser 19.1.9 → 19.2.1

package/dist/browser.js

@@ -14,7 +14,7 @@ import { isStaleSingletonLock } from "./utils.js";
 import { join, dirname } from "path";
 import { execSync } from "child_process";
 import { mergeConfig, getPaths, ensureDirectories } from "./config.js";
-import { BUILTIN_PERSONAS, getPersona } from "./personas.js";
+import { getPersonaOrRefuse } from "./personas.js";
 import { DEVICE_PRESETS, LOCATION_PRESETS, CBrowserErrorCode } from "./types.js";
 import { runCognitiveJourney, isApiKeyConfigured, } from "./cognitive/index.js";
 import { SessionManager } from "./browser/session-manager.js";
@@ -5176,7 +5176,7 @@ For more help: https://playwright.dev/docs/browsers
         // Heuristic mode (no API key or cognitive journey failed)
         // NOTE: This is simplified exploration. For realistic user simulation,
         // configure an API key: npx cbrowser config set-api-key YOUR_KEY
-        const persona = getPersona(personaName) || BUILTIN_PERSONAS["first-timer"];
+        const persona = getPersonaOrRefuse(personaName);
         this.currentPersona = persona;
         // Set viewport based on persona
         if (persona.context?.viewport) {
@@ -5897,6 +5897,24 @@ For more help: https://playwright.dev/docs/browsers
             await h.dispose();
         return el;
     }
+    /**
+     * The click gate's verdict on the element `selector` resolves to, judged on the element ITSELF (no
+     * hit-test, so nothing scrolls). find_element_by_intent reports it as `zone`. A real click is additionally
+     * judged where the pointer lands, so a container (a card, a section) can read yellow here and still be
+     * refused when the control at its centre is red. Resolves `selector` as CSS, not through the text-first
+     * click resolver or the self-healing cache. The finder's selectors are built so that the text-first resolver
+     * reaches the same element (no form that is also page text, no lone tag), but click() consults the self-healing
+     * cache before resolving, so a stale cache entry for the same selector string can still send click() to a
+     * different element than the one judged here.
+     */
+    async elementZone(selector) {
+        const page = await this.getPage();
+        const loc = page.locator(selector).first();
+        if ((await loc.count().catch(() => 0)) === 0)
+            return null;
+        const el = await this.classifyElement(loc, { skipHit: true });
+        return el ? { zone: el.zone, label: el.label } : null;
+    }
     /**
      * Refusal message when a click at viewport point (x, y) would activate a red-zone control, else null.
      * Used by the NL test runner's "click at X, Y".