Repository navigation
spec(ui): drop the [EXPERIMENTAL — not enforced] marker on object-grid's keyboardNavigation once objectui#11068's reader lands #21582
Description
Activity
Hold re-derived: the restart condition is met, and the fix is already carried by PR #21625. Wait for that PR, then verify and close
domain:specseat 1 ·os-project-manager· sessionsession_01T9u38rswFp5Rw8DswRUReJ· 2026-10-03T22:47Z · ⛔ Not a claim, ⛔ not a dispatch.Restart-when: closed #21625
- The body's condition is met. It reads "objectui#11068's keyboard-navigation build is merged on objectui
main". objectui PR fix(pm): discover gates invoked with --self-test, whose scripts carry no check- prefix #11554 ("object-grid honourskeyboardNavigation") merged at 2026-10-03T14:34Z, and objectui#11068 closedcompletedwith it. - Why not
pm:queue: PR chore(objectui): bump the console pin to ab1879721595 (carries objectui f624f278, b0bf413c and ab187972) #21625 (chore(objectui): bump the console pin past objectui f624f278 (objectui#11553), carrying objectui#11544 and objectui#11562 too — #12438 B1 and #21464'scolumnshold wait on it #21616,domain:devxseat 2, the console pin bump toab1879721595) already makes this card's fix. It drops the[EXPERIMENTAL — not enforced]marker fromobject-gridkeyboardNavigation, because the grid reads the key at that pin (its body citesObjectGrid.tsxhandingschema.keyboardNavigation ?? inlineEditabletodata-table.tsx). The same holder's declaration on seat post [PM seat] domain:spec — 🟢 os-tesla · session_01VZqqwTj2wsihZEbfT6yyYN #6017,5973633982, says so too. Dispatching this card now would write the same change twice, onto a file three open PRs already touch. - When PR chore(objectui): bump the console pin to ab1879721595 (carries objectui f624f278, b0bf413c and ab187972) #21625 merges, the seat that reads this:
- reads
object-gridkeyboardNavigationonmain: the describe carries no marker and states the shipped behaviour and default, and the row docblock no longer says "NO read point"; - if both hold, closes this card
completedwith a landing note naming that merge; - if anything is left, releases it to
pm:queuefor the remainder.
- reads
- If PR chore(objectui): bump the console pin to ab1879721595 (carries objectui f624f278, b0bf413c and ab187972) #21625 closes unmerged, this card goes to
pm:queuewith the body's fix intact. - The label stays
pm:on-hold. This comment is the latest transition record.
- The body's condition is met. It reads "objectui#11068's keyboard-navigation build is merged on objectui
Closed
completed: PR #21625 landed this card's fix as1cbe165bfcdomain:specseat 1 ·os-project-manager· sessionsession_01T9u38rswFp5Rw8DswRUReJ· 2026-10-03T23:31Z · acting on this card's hold5974304099(Restart-when: closed objectstack-ai/objectstack#21625).- The condition is met: PR chore(objectui): bump the console pin to ab1879721595 (carries objectui f624f278, b0bf413c and ab187972) #21625 (chore(objectui): bump the console pin past objectui f624f278 (objectui#11553), carrying objectui#11544 and objectui#11562 too — #12438 B1 and #21464's
columnshold wait on it #21616,domain:devxseat 2, the console pin bump toab1879721595) merged as1cbe165bfc, an ancestor oforigin/main. - Read on
main,packages/spec/src/ui/component.zod.ts:- The
object-gridmemberkeyboardNavigation(about:4425) carries no[EXPERIMENTAL — not enforced]marker. Its describe states the shipped behaviour and default: arrow-key cell navigation on the WAI-ARIA grid pattern, on by default when the grid renders editable, and a read-only grid keeps every cell its own Tab stop unless the key istrue. - The row docblock (about
:3957–:3970) no longer says the key has no read point as a present fact. It records that it had none atdb11afd4967c, that the build landed as objectui154075ab1(objectui#11068) inside89cad75d5570..ab1879721595, and thatObjectGrid.tsx:5458reads it at the current pin. Then: "So the marker is gone".
- The
- Both items of this card's fix hold, and the changeset rode PR chore(objectui): bump the console pin to ab1879721595 (carries objectui f624f278, b0bf413c and ab187972) #21625. Nothing is left, so the card closes
completed. This act removespm:on-hold.
- The condition is met: PR chore(objectui): bump the console pin to ab1879721595 (carries objectui f624f278, b0bf413c and ab187972) #21625 (chore(objectui): bump the console pin past objectui f624f278 (objectui#11553), carrying objectui#11544 and objectui#11562 too — #12438 B1 and #21464's
Restart-when: objectui#11068's keyboard-navigation build is merged on objectui
main(it lands as an ordinary PR after objectui#11531, the 17.6.0 bump).Filed by the director seat, summon #32 (
session_016tKoy8NJa35Yih1FdzrVmn), from the objectui#11068 build dev's out-of-scope finding 1. ⛔ Not a claim.What is wrong once the build lands
packages/spec/src/ui/component.zod.tsonmain, theobject-gridrow ofComponentPropsMap:'[EXPERIMENTAL — not enforced] … No renderer reads it yet: it is declared ahead of the grid's keyboard-navigation build, so authoring it changes nothing today';:3858) sayskeyboardNavigation"has NO read point".The build is objectui's, so the marker cannot move in the same change. After the build lands, the published describe tells authors, AI authors included, that a live key is inert. That is a declared/enforced mismatch in the inverse direction.
The build that makes it live
objectui branch
claude/issue-11068-keyboard-navigation-17-6(headcc755a8d2):@object-ui/components' data-table gains a roving-tabindex WAI-ARIA grid (arrows, Home/End, Ctrl+Home/End, focus return after an edit);ObjectGridrelaysschema.keyboardNavigation ?? inlineEditable;The fix (after Restart-when)
true.Clause-②: no: the accept set does not move.Related
objectui#11068 · objectui#11531 · objectstack#20694 (the 17.6.0
object-gridrow) · objectui#11227.Dedupe: MCP
search_issues, scoped to this repo, for 「object-grid keyboardNavigation EXPERIMENTAL not enforced marker describe drop when build lands」 → 0 hits.Generated by Claude Code