[vjeux]

Exact decision needed

None yet: an open API question on component:Tooltip, whether triggerBehavior="toggle" keeps taking over its child button's press implicitly, or moves to an explicit pattern where the caller's button calls show() and hide().

Existing authority searched

component:Tooltip (FR9–FR10, DEC log, Open questions: "None."), component:InfoTip, and useTooltip's TooltipReturn; useHoverCard already returns show() and hide(), a precedent for the explicit option. Open PRs that edit Tooltip.spec.md (#9291, #9361) leave its Open questions section alone. No current claim decides between the two patterns.

Decision

No decision: OQ1 records the question (human-api, low priority), with no code change.

Owner's text, adjusted for accuracy at main

The owner's text was: "OQ — Implicit toggle. With triggerBehavior="toggle", Tooltip takes over its child button's press implicitly. Open: whether toggle stays implicit or moves to the explicit pattern InfoTip uses, where the caller's Button calls useTooltip's show() and hide()."

Two facts differ at main 4a8a76e, so the record words them as possibilities:

• InfoTip composes <Tooltip triggerBehavior="toggle">, the implicit path itself.
• useTooltip returns ref, positionRef, interactionRef, anchorId, describedBy and renderTooltip, with no show() or hide().

Rejected alternatives

None; the question stays open.

Claim scope and non-goals

Only Open questions changes; no behavior, API or verification claim moves.

Evidence and implementation relationship

None; no implementation PR.

Writing rubric results

• R1 narration: none; OQ1 states the system in the present tense.
• R2 research in the record: none.
• R3 evidence naming a change: none.
• R4 rejected alternatives over one line or outside a decision: none.
• R5 pull request or issue references remaining: none.
• R6 ruled open questions still listing options: none; OQ1 is unanswered and keeps its two options.

Scope

• This PR contains specification records only.
• It records observable behavior and preserves equivalent internal implementations.
• Any named internal mechanism is intentionally public, names its dependent caller/system, and explains why an equivalent implementation would not satisfy the contract.
• Verification states the evidence layer and failure signal without prescribing CI job/workflow topology.
• It records one intentional durable decision, not a rescue for a separable tagalong.
• The canonical knowledge owner, affected current claims, and overlapping open work are named; any ownership collision is resolved or called out for human decision.
• Adjacent API, visual, accessibility, composition, and implementation facts remain outside scope unless this exact decision depends on them.
• Public text and artifacts contain no internal Meta context.

Validation

At 3ccce21: pnpm check:knowledge, Prettier and git diff --check pass. The owner-gated record needs an engineering owner's /approve-spec.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
astryx	Ready	Preview	Nov 3, 2026 5:23am UTC

[astracat-bot]

AI review status for this pull request.

Review status	Updated
🔄 In progress (for maintainers only)	Nov 3, 2026, 5:13 AM UTC

[vjeux]

Closing: covered by #9711's Tooltip open question.