fix(v3): normalize CUA coordinates to actual viewport

[miguelg719]

why

Verified Browserbase mobile sessions can expose a CSS viewport such as 384x696 even when the requested viewport differs. Google CUA was instead normalizing model coordinates against a hard-coded 1288x711 viewport, which converted valid taps into off-screen mouse coordinates and prevented touch-only controls from working.

what changed

• Add a shared V3 viewport resolver: use an explicitly configured viewport without probing, otherwise probe the active page, then fall back to the default.
• Use the shared resolver in both direct CUA and hybrid Google coordinate normalization, removing both Verified-mode 1288x711 special cases.
• Resolve the viewport once per fillFormVision execution and reuse it across all fields.
• Deduplicate configured viewport lookup behind rawConfiguredViewport.
• Cover configured, probed, default, direct CUA, and hybrid coordinate paths without constructing the Google SDK client.

test plan

• pnpm --filter @browserbasehq/stagehand build:esm
• pnpm --filter @browserbasehq/stagehand exec vitest run dist/esm/tests/unit/touch-cua-routing.test.js dist/esm/tests/unit/coordinate-normalization.test.js dist/esm/tests/unit/touch-tool-routing.test.js
• pnpm --filter @browserbasehq/stagehand typecheck
• pnpm exec eslint on all changed production and test files
• Full unit suite: 909 passed; the four FlowLogger failures reproduce unchanged on origin/v3
• Verified through the Browserbase path with disableAPI=true: https://www.browserbase.com/sessions/164a55eb-1cf6-4267-86b2-90e821a7c119

[changeset-bot]

🦋 Changeset detected

Latest commit: 80ea5e2

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@browserbasehq/stagehand	Patch
@browserbasehq/stagehand-evals	Patch
@browserbasehq/stagehand-server-v3	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[cubic-dev-ai]

All reported issues were addressed across 2 files

Architecture diagram

sequenceDiagram
    participant V3 as V3CuaAgentHandler
    participant Page as Active Page (Browser)
    participant Google as GoogleCUAClient
    participant Test as Regression Test

    Note over V3,Google: CUA Coordinate Normalization Flow

    alt Normalization for all CUA clients (NEW unified path)
        V3->>Page: awaitActivePage()
        Page-->>V3: page reference
        V3->>Page: page.mainFrame().evaluate() for window.innerWidth/innerHeight
        Page-->>V3: { w: 384, h: 696 } (actual CSS viewport)
        alt Valid dimensions returned
            V3->>Google: setViewport(384, 696)
            Google-->>V3: viewport updated
        else w or h is 0/undefined
            V3->>V3: skip update (empty catch block)
        end
    end

    Note over V3,Test: Key behavior: coordinates now match actual rendered viewport instead of hard-coded 1288x711 (old Verified mode)

    alt Regression test: Google CUA with mobile viewport mismatch
        Test->>V3: create handler with isVerified=true, configuredViewport=430x932
        Test->>Test: spy on GoogleCUAClient.setViewport()
        V3->>Page: awaitActivePage()
        Page-->>V3: page with 384x696 CSS viewport
        V3->>Google: setViewport(384, 696)
        Google-->>V3: viewport set
        Test->>Test: expect(setViewport).toHaveBeenCalledWith(384, 696)
        Note over Test: Verifies actual mobile viewport (384x696) overrides<br/>configured (430x932) and old 1288x711 fallback
    end

Loading

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>