The keydown, from whatever host captured it.
The current bus state (caller checks armedness policy; this checks mode === 'point').
The sheet the user is POINTING AT — always required, always stamped (the inverted
reporting rule: a picker's report carries its scope unconditionally; the consumer localizes). A grid
pane passes its own sheet; an input host passes the workbook's DISPLAYED sheet (Excel: keyboard
pointing targets the sheet you are looking at). The seed — and, on a re-scope, the active
reference — is re-homed here before the move, the same semantics as the mouse path's pane-side
stamping (scopeDrawnRanges).
true when the key was consumed (a point-nav key while 'point' is armed).
The shared point-mode navigation keymap — the reference-picking keys every host routes the same way, so key routing "just works" wherever focus happens to be (the inline editor, the formula bar, a grid pane layer, a dialog range field):
navigate)navigateselect)navigatecontentful)selectRegioncolumn)selectRegionrow)selectRegionboth)Only these are consumed (
preventDefault+stopPropagation); anything else returnsfalseand the host's own handling proceeds. Done/leave keys (Enter / Tab / Escape and their variants) are deliberately NOT here — they are host policy: a focused editor commits/cancels through its own keymap, the grid layer routes them to the bus's producer-suppliedonDone, and a dialog picker wants them back in the dialog. A shared table for them would steal exactly the keys hosts must own.Operates purely on the bus state's ReferenceModeState.selection — no editor, no session. When the caret isn't on a reference yet (INSERT:
rangeIndex < 0) the first key seeds an active range at the selection's anchor cell (fenced — see isReferencePointSeeding) and then navigates, so the write-back inserts the navigated range, even for the first keystroke.