[jameskraus]

Keep the PR menu usable after a click. Base UI inserts hidden elements that break the button's :last-child alignment. The button moves before mouse-up, closing the menu. Target the menu trigger directly instead.

Adds one browser regression, with none removed. It lets the menu render before mouse-up, selects Convert to draft, and verifies the draft state. Real pointer hit-testing catches what jsdom misses. It fails before the fix and passes in Chromium and WebKit across both themes, narrow and wide layouts, and enlarged text.

Before/after demo uses fictional data.

pr-demo.mp4

Draft pending native desktop and human acceptance.

[wesbillman]

🤖 Carl, an automated reviewer, commenting via Wes’s GitHub account.

No blockers. Targeting [aria-haspopup="menu"] directly is the right fix: the menu trigger is the only such child of .pullActions, and it matches the existing [aria-haspopup="menu"] selectors in SoloWorkspaces.module.css.

Validation at 075293a: CI is green. Locally, the new browser journey passes in Chromium. With only the CSS change reverted, it fails in both Chromium and WebKit at item.click because the menu has already closed. So the test does guard this regression.

Remaining gate is the one in the description: native desktop and human acceptance.

[kalvinnchau]

🤖 Code review at 075293a: no findings.

• Root cause confirmed: Base UI MenuTrigger wraps the trigger in pre/post FocusGuard spans only while open, so :last-child stops matching on open and the trigger loses margin-left: auto mid-press. The guards are position: fixed (visuallyHidden), so they are out of flex flow; matching [aria-haspopup="menu"] (set unconditionally by MenuTrigger) keeps the layout identical open and closed. No other child of .pullActions carries that attribute.
• Ran tests/browser/github-actions.spec.mjs: passes in chromium and webkit at head; with the pre-fix selector restored it fails in both (Convert to draft click times out after the menu closes). Biome clean on the changed files; CI green.

Scores: correctness 10, elegance 9, minimalness 9. The 110-line fixture is large next to a one-line fix, but it follows the existing tests/fixtures/*.tsx pattern and real pointer hit-testing is the only way to cover this. Non-blocking: JSON.parse(JSON.stringify(...)) in the fixture only serves to produce an untyped value for the generic GitHubCli return; a cast would say that more directly.