Interface CommandAnchorProviderProps

Display cadence (ms); coalesces anchor + contribution changes for this container.

Bound this container's focus walk to an element: the tracker only follows focus that lands inside it, so focus elsewhere leaves the anchor where it was (a script pane's toolbar stays live while the user clicks into the grid). The consumer-side counterpart of a scope's CommandScopeProviderProps.elementRef — same element, different job: that one decides which commands a keystroke may reach, this one decides where the anchor may move.

'synthetic' delivery bounds the tracker to its own key seam when this is omitted, keeping the anchor's region and the key-delivery region identical.

Keystroke delivery for this container's resolver:

• true (default): auto-attach native keystroke handling to the tracker's region element (CommandResolverOptions.keyBindings).
• false: the host delivers keys to the resolver's dispatchKey itself — e.g. a grid routing them through its synthetic Stage responder chain, or a toolbar-only container with no keystroke surface at all.
• 'synthetic': this provider renders the delivery seam itself — a layout-inert (display:contents) wrapper whose synthetic onKeyDown feeds dispatchKey. In the one React keystroke bubble it is the outermost handler — the container's "dispatcher of last resort" — so an inner layer's synthetic stopPropagation pre-empts it (a native ancestor listener would fire ahead of every React handler and could not be pre-empted; that ordering bug is why this mode exists). The tracker (if it implements ActivationTracker.attach) is bounded to the same element, keeping the anchor's focus region and the key-delivery region identical.

The bounded-walk terminal — this container's topmost node (e.g. the sheet scope for a context menu). Omit ⇒ walk to the true tree root (the studio default). See CommandResolverOptions.root.

This container's activation — its anchor source (region-scoped focus, or manual).