Context
#19657's class probe of the popup group (analysis). --screen-info={1920x1080} came from #19288, which replaced headless Chrome's 800×600 default because the window manager clamps script-moved popups into the screen.
The Problem
At 1920×1080, the journeys that drive a popup beside a 1280×720 main window still run out of screen. The window manager refuses or clamps the popup's moves.
WorkstationDragAffordancesNL:388 drives its re-exited vessel to about (1620, 1010):
- alone, every
window.moveTo was refused, and its own guard skips the test ("native pointer-follow is stage-bound here");
- in the full tier the moves were clamped, so the test failed with
{x: 114, y: 0} against the expected {x: 120, y: 70}.
One-runner A/Bs, interleaved, comparing a 1920×1080 screen with a 2560×1440 one:
| Test |
1920×1080 |
2560×1440 |
WorkstationDragAffordancesNL:388 (run) |
skipped 3/3 |
passed 3/3 |
WorkstationFilmTourNL:302 (run) |
0/2 |
2/2 |
WorkstationFilmTourNL:223 |
0/2 |
1/2 |
WorkstationNL:2604 |
0/2 |
2/2 |
The FilmTour file also ran in 2.5–4.7 min instead of 7. Its failures waited out 200 s receipts.
WorkstationReclaimEmbodimentNL:148, WorkstationPopOutPaneIdentityNL, LegacyPopupReturnNL and WorkstationPopOutSparklinesNL:74 were red at similar rates on both screens, so their causes lie elsewhere (#19657).
The Architectural Reality
test/playwright/e2e/utils/gpuIntent.mjs BASE_LAUNCH_ARGS is the one launch-argument list, for every e2e tier and local runs.- The specs that read the screen adapt to it:
WorkstationNativePopupOverPopupNL takes its wide branch from 980 px;DockPlacementNL asserts placement inside the screen.
- The specs that set 1920×1080 set the viewport or
contextOptions.screen, not the window manager's bounds.
The Fix
Set --screen-info={2560x1440} and update the JSDoc's reason.
Acceptance Criteria
Out of Scope
- Dropping FilmTour's quarantine entries: that follows a dedicated run once this lands.
- The other popup-group causes (#19657).
Related
#19657 · #19655 · #19675 (also edits BASE_LAUNCH_ARGS, on a different line) · #19288
Live latest-open sweep: checked the latest 20 open issues at 2026-10-12T19:53Z; no equivalent found. Issue search for screen-info: none.
MC sweep: "headless Chrome screen-info 1920x1080 popup window moveTo clamped window manager e2e". It surfaced #19288 (the 800→1920 change and its clamp measurement) and #19309's wide-branch control; no contrary decision.
Own-assignment sweep: #19657 is the parent outcome.
Origin Session ID: 02040656-932a-48c8-8894-6f43d0368663
Context
#19657's class probe of the popup group (analysis).
--screen-info={1920x1080}came from#19288, which replaced headless Chrome's 800×600 default because the window manager clamps script-moved popups into the screen.The Problem
At 1920×1080, the journeys that drive a popup beside a 1280×720 main window still run out of screen. The window manager refuses or clamps the popup's moves.
WorkstationDragAffordancesNL:388drives its re-exited vessel to about (1620, 1010):window.moveTowas refused, and its own guard skips the test ("native pointer-follow is stage-bound here");{x: 114, y: 0}against the expected{x: 120, y: 70}.One-runner A/Bs, interleaved, comparing a 1920×1080 screen with a 2560×1440 one:
WorkstationDragAffordancesNL:388(run)WorkstationFilmTourNL:302(run)WorkstationFilmTourNL:223WorkstationNL:2604The FilmTour file also ran in 2.5–4.7 min instead of 7. Its failures waited out 200 s receipts.
WorkstationReclaimEmbodimentNL:148,WorkstationPopOutPaneIdentityNL,LegacyPopupReturnNLandWorkstationPopOutSparklinesNL:74were red at similar rates on both screens, so their causes lie elsewhere (#19657).The Architectural Reality
test/playwright/e2e/utils/gpuIntent.mjsBASE_LAUNCH_ARGSis the one launch-argument list, for every e2e tier and local runs.WorkstationNativePopupOverPopupNLtakes its wide branch from 980 px;DockPlacementNLasserts placement inside the screen.contextOptions.screen, not the window manager's bounds.The Fix
Set
--screen-info={2560x1440}and update the JSDoc's reason.Acceptance Criteria
BASE_LAUNCH_ARGSgives headless Chrome a 2560×1440 screen, and the JSDoc says why: the multi-window journeys need room beside a 1280×720 window.WorkstationDragAffordancesNL:388runs instead of skipping.Out of Scope
Related
#19657 · #19655 · #19675 (also edits
BASE_LAUNCH_ARGS, on a different line) ·#19288Live latest-open sweep: checked the latest 20 open issues at 2026-10-12T19:53Z; no equivalent found. Issue search for
screen-info: none. MC sweep: "headless Chrome screen-info 1920x1080 popup window moveTo clamped window manager e2e". It surfaced#19288(the 800→1920 change and its clamp measurement) and#19309's wide-branch control; no contrary decision. Own-assignment sweep: #19657 is the parent outcome.Origin Session ID: 02040656-932a-48c8-8894-6f43d0368663