Control-Option-N reaches each display in screen order on a Mac with three displays#417

opened4h agobySSamanyu Das

Note

🤖 Claude Opus 5.5 responding on behalf of Sam

Outcome

Control-Option-N is checked on a real Mac with three displays, so someone with three displays can trust it to reach each of them in screen order. This is the last open check on #333, whose engine tests and two-display live check pass on main at abe13aa1.

Context

  • #333 defines the order: left to right by left edge, then top to bottom, then display ID, wrapping from the last display to the first.
  • paneru#149 and #416 shipped it.
  • Sam's test Mac has two displays. A friend's Mac with an M5 Pro and three displays may run the check.

Acceptance criteria

  • On a build of main at or after abe13aa1, with three displays side by side, verify-miri presses ⌃⌥N six times, and fixture-1 visits each display once per cycle in screen order. Engine focus and macOS focus are on fixture-1 after each press.
  • The same check passes with one display that touches another only at a corner.
  • The display arrangement after each run matches the record taken before it.
  • The results, with the Mac model, macOS version, and each display's ID, origin, and size, are in a comment on #333.

Verification level

Hardware: a Mac with three displays, with Accessibility granted by hand to Miri Developer and to the terminal that runs verify-miri. No code change, so no make target.

Out of scope

Four or more displays, which the engine tests cover.

Note

🤖 Claude Opus 5.5 responding on behalf of Sam

The test prompt for this check is in a secret gist: https://gist.github.com/samanyudas/2b7b813670b81b10ef09c74cc516d0e4

Sam plans to ask a friend with an M5 Pro Mac and three displays to run it when the app is almost done, so this issue is blocked by #82.

The prompt has the friend's coding agent build the latest main. It refuses a build without abe13aa1 or engine f1c14be. Then it presses ⌃⌥N six times with verify-miri, with the displays side by side and, if the owner agrees, with one display touching another only at a corner. It returns a plain-text report: the hardware, the commits, and each display's ID, origin, and size, plus one row per press. It posts nothing to GitHub, changes no macOS settings, and asks the owner before it installs anything or moves a display.

When the report arrives, post its results on #333 and tick the criteria here.