Description
Current reconciliation - 2026-11-09
Audited against main 666e32983.
Open: trigger-based Menu is now delivered, but context-menu opening is not. #4386 ships the normal Menu/MenuButton/Popover contracts. Menu's SPEC explicitly defers secondary-click/keyboard/assistive context invocation and point anchoring here. Modern macOS/Windows rect/point support is not public Menu admission, and the Win32 adapter still supports View anchors only.
Next: review the context-opening amendment, qualify each input transport and invoking-element focus return, and establish point placement on all four desktop endpoints with #4375/#4384. Do not substitute primary presses or declare Win32 point anchoring supported from the legacy anchorRect prop alone.
Source: packages/agentic/components/src/components/menu/SPEC.md, packages/agentic/native-core/references/modern-components.md, and packages/agentic/components/src/components/popover/SPEC.md.
Evidence limits: Source and committed-test inspection only; package/build/native tests were not run in this reconciliation. Earlier native results remain revision-specific; skips, unsupported outcomes, and input-lane exclusions are not passes.
Historical issue scope and acceptance (retained; current reconciliation above supersedes stale status and dependencies)
Goal
Add context-menu presentation to the agentic Menu: opening a Menu from a secondary click or a keyboard context-menu invocation, anchored at the invocation point or element. This scope was deferred from the first Menu delivery by owner decision on 2026-10-16. Part of #4274. Trigger-anchored Menu, MenuButton, and Popover delivery remain #4232, #4231, and #4236; do not duplicate them.
Observed baseline — 2026-10-16
- The modern native-core
Callout(/macosand/windowspreviews) already acceptsview, owner-relativerect, and owner-relativepointanchors (packages/agentic/native-core/src/components/callout/Callout.types.ts). No agentic component exposes point anchoring, and no component detects secondary-click or context-menu-key input. - The legacy Win32
Calloutaccepts ananchorRectin DIPs relative to the React surface origin (packages/agentic/native-core/src/legacy/callout/Callout.types.ts). Point anchoring on the prebuilt Office host is unverified. - The first Menu delivery (Components: Generate Menu #4232) anchors to its trigger view only.
Acceptance
- Review a Menu contract amendment covering context-menu opening sources (secondary click, the platform context-menu key or shortcut, and assistive-technology show-menu actions), point versus element anchoring, placement with flip and clamping around a point, entry focus, focus return to the invoking element, and dismissal.
- Qualify secondary-click and context-menu-key delivery on macOS Paper and Fabric, Windows Fabric, and Win32. Record unsupported paths explicitly; do not emulate secondary input with primary presses.
- Expose point anchoring through the public Menu API (and Popover, if approved) only after native point anchoring is qualified on every platform, including Win32, with RTL, display scaling, multiple monitors, and scrolled anchors (coordinate with Components: Complete Callout geometry, lifecycle, and assistive-technology qualification #4375).
- Ship on all desktop endpoints together (macOS Paper and Fabric, Windows Fabric, Win32), matching the platform policy for the Menu family.
- Add stories with top-level
wdiocases and record per-endpoint executed, passed, failed, and skipped counts; skips are not passes.
Evidence
- Deferred during Popover, Menu, MenuButton, and Dropdown implementation planning against
maine2092f9df3fd4fafc141c696ca0e49e690d69cd1. - The pinned Flex Menu guidance includes context-menu opening; the Components: Generate Menu #4232 contract should record it as deferred scope linked here rather than as an unsupported promise.
Activity