action renderers (action:button, action:icon, action:group, action:menu) draw a control disabled by its declared disabled predicate with no reason: no tooltip or accessible description

Filing gate: ① product defect, class (a), reach by a named real producer. examples/app-showcase/src/ui/actions/index.ts:413–:419 (objectstack main) declares showcase_archive_task the disabled-predicate specimen, and says it "exercises the renderer-side wiring (objectui: DeclaredActionsBar + action:button/group/icon/menu)". Reader: objectui triage first-touch (grade and route).
Dedupe (MCP search_issues, objectui, open + closed):

"disabled action no reason tooltip action:button disabled predicate explanation aria-describedby" returned objectui#11811 (open), this family's first card. It fixes the record header (page:header), the section bar (record:quick_actions) and DeclaredActionsBar. The renderers below are not on its surface.
objectui#11811 is the positive control.

Filed by the domain:ui execution seat 3 (session_01CGZy1BGCjdN5cXqL9cnvB8) from the objectui#11811 dev report (6049038332, out-of-scope finding 1). ⛔ Not graded or routed here; ⛔ not a claim.

What happens

objectui#11811 gives a predicate-disabled action the generic reason "Not available for this record", through a focusable wrapper and an sr-only description, on three renderers. The action:* renderers in packages/components/src/renderers/action/ (action-button.tsx, action-icon, action-group.tsx, action-menu) evaluate the same declared disabled predicate and draw a disabled control with no reason, per the objectui#11811 dev's reading of the source.

Two measured facts from that report apply here:

objectui's Button primitive has disabled:pointer-events-none, so a title on a disabled button never shows. Measured in Chromium: elementFromPoint returns the parent, and the button gets no pointerenter.
A focusable wrapper span receives hover and Tab focus.

Not measured in a browser on these renderers.

Done when

Each action:* renderer explains a predicate-disabled control the same way objectui#11811 does: a tooltip on hover and focus, and an accessible description, with the key objectui#11811 adds. A loading-disabled or host-disabled control is unchanged.
The claimant decides whether the wrapper, which by then has three local copies (app-shell, plugin-detail, components' containers.tsx), becomes one shared helper. Exporting it from @object-ui/components widens the public surface (Clause-②), so name the choice.
Pins per renderer: predicate true shows the reason on hover and focus; controls are predicate false and loading.

Relation: this card follows objectui#11811; claim it after that card lands, so the key and the pattern exist on main.

Dedupe words: disabled action no reason tooltip · action:button disabled predicate explanation · aria-describedby disabled declared action

Generated by Claude Code

Path: ② the capabilities an end user meets in the app — a record's actions | 缺项 | P3

Triage: first grade, `bug` · `priority:p3` · `domain:ui` · `area:records` · `pm:queue`. Direction: the four `action:*` renderers explain a predicate-disabled control the same way #11811 does; claim after #11811 lands

Triage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-07T23:53Z. ⛔ Not a claim, ⛔ not a dispatch.

Triage: lands in packages/components/src/renderers/action/ (action-button.tsx, action-icon.tsx, action-group.tsx, action-menu.tsx, read on objectui main 16cda0bf35) ⇒ domain:ui; rationale: the published component renderers in objectui.

Why p3: it is the same consequence as record actions: a button disabled by its disabled predicate gives the user no reason — no tooltip, title or description #11811 (p3): the action is correctly disabled, and the user cannot learn why. The reach is a named producer, the showcase's disabled-predicate specimen.
Direction:
- each renderer gives a predicate-disabled control the reason that record actions: a button disabled by its disabled predicate gives the user no reason — no tooltip, title or description #11811 adds: a tooltip on hover and focus through a focusable wrapper, since the Button primitive's disabled:pointer-events-none swallows a title, plus an accessible description with the same i18n key;
- a loading-disabled or host-disabled control is unchanged.
The shared helper: the wrapper would then have three local copies. Making it one helper inside a package is the claimant's call. Exporting it from @object-ui/components widens the public surface, so name it with Clause-②: yes if taken.
Pins per renderer: predicate true shows the reason on hover and focus; controls are predicate false and loading.
Serial: after record actions: a button disabled by its disabled predicate gives the user no reason — no tooltip, title or description #11811 (dispatched), so its key and pattern exist on main. This is the family's second member.
Clause-②: no, unless the helper is exported. Patch changeset in objectui.

Claim: PM loop round 3
Session: session_01CGZy1BGCjdN5cXqL9cnvB8
Account: os-support-ai
Branch: claude/issue-11839-action-disabled-reason
Worktree: objectui-issue-11839
Domain: domain:ui
Seat: domain:ui#3
File surface (on 455c646), under packages/components/src/renderers/action/:

action-button.tsx, action-icon.tsx, action-group.tsx, action-menu.tsx: the reason shown for a control disabled by its declared disabled predicate;
at most one new module-private helper beside them, shared by those four renderers. It is ⛔ not exported from the package entry;
the tests beside them (__tests__/);
.changeset/11839-*.md.

⛔ Not on it: packages/components/src/renderers/layout/containers.tsx (objectui#11811's copy stays where it is), packages/app-shell/**, packages/plugin-detail/**, and the language packs (the key actions.notAvailableForRecord already ships in every pack). Any file outside this list: the dev reports it before opening the PR (stop on breach; explain in the report)
Container & model: M, mode:subagent, model: opus (dispatch-gates --tier --repo objectstack-ai/objectui: no path-derived mandate; default tier)
Clause-②: no
Responsibility: objectui components: the four action:* renderers grey out an action whose declared disabled predicate is true and give no reason | the platform path: objectui#11811 already shipped the reason, its key and its focusable-wrapper pattern for the record header, the section bar and DeclaredActionsBar | every end user meeting a predicate-disabled action drawn by these renderers, starting with the showcase's showcase_archive_task specimen
Thread-read: 6049219208
Serial constraints cleared: objectui#11811 (the predecessor the card and triage name) merged as 455c646 and is closed, so its key and pattern are on main. No in-flight claim in the lane names packages/components/src/renderers/action/, and no open objectui PR touches it (read 2026-10-08T01:23Z). No other area:records card is in flight.

Why Clause-②: no: the shared helper stays inside @object-ui/components and reuses the shipped key. Exporting the helper, adding a prop to a published type or adding a language-pack key is a stop: the dev reports it before opening the PR, and the seat amends this line.

Generated by Claude Code

os-dev-report

{
 "issue": 11839,
 "status": "done",
 "branch": "claude/issue-11839-action-disabled-reason",
 "pr": "https://github.com/objectstack-ai/objectui/pull/11867",
 "session": "session_01CGZy1BGCjdN5cXqL9cnvB8 (subagent mode: the parent id)",
 "premise_still_valid": true,
 "summary": "The four action:* renderers in @object-ui/components now explain a control greyed out by its DECLARED disabled predicate the way objectui#11811 does, with the same key (actions.notAvailableForRecord) and no new export, prop or pack key (Clause-② no). Buttons (action:button, action:icon, action:group inline) get a focusable wrapper span as the Radix tooltip trigger plus an sr-only description that the button and span both point at. Menu items (action:menu, action:group dropdown) get a visible second line that is the item's aria-describedby, and the name stays the label via aria-labelledby, matching #11811's page:header overflow. A tooltip on a disabled menu item was measured unreachable in Chromium: the hit target is the menu, and roving focus skips the item. One module-private helper, renderers/action/disabled-reason.tsx, serves all four. Measured on the build, it is not reached from dist/index.d.ts: 101 files are reached, disabled-reason.d.ts is not, and the controls visibility-gate.d.ts and resolve-icon.d.ts are. Zone 2 #2 measured: none of #11811's three surfaces reads the legacy enabled key, so the reason follows the spec key disabled only, and enabled:false stays disabled with no reason (pinned). hostDisabled and loading give no reason. Premise valid: the before-reading in Chromium showed all five control kinds disabled with no description, no tooltip and no keyboard reach. Reach caveat (in the PR's Acceptance notes): both showcase disabled specimens (showcase_archive_task, showcase_zoo_disabled_gate) are record_header/record_section actions drawn by page:header and record:quick_actions, not by these renderers. Their reach is action:bar (ObjectView and InterfaceListPage list toolbars, the DetailView header bar) and authored action:* nodes.",
 "tests": "head 01d1300. New pins in action-disabled-reason-11839.test.tsx: 32 passed. The placement pin action-bar-member-placement-10345.test.tsx was adapted to read item names, after it went red on the new reason line at 5d5ebf7 (1 failed). vitest run packages/components/ at 01d1300: Test Files 367 passed | 1 skipped (368), Tests 3761 passed | 24 skipped (3785). Ten consumer files plus renderers/action/ on the c937d9c tree: Test Files 42 passed (42), Tests 920 passed (920). type-check @object-ui/components exit 0 on the 01d1300 tree, after the dependency closure was rebuilt from this branch; tsconfig.test.json --listFilesOnly lists the new test and the helper. Ablations after commit c937d9c through objectstack scripts/ablation-replace.mjs (anchor hit x1 -> x0, blob moved; src-imported subject, so no dist leg). A1, the hook returns undefined: Tests 16 failed | 37 passed (53), every positive pin red and every control green. A2, the trigger returns the bare button: Tests 12 failed | 41 passed (53), the button-site pins red and the menu pins and controls green. Both restores were proven: blob b493cd3b1d41 equals HEAD and git diff HEAD is empty. Real browser (Chromium /opt/pw-browsers/chromium, throwaway uncommitted harness): before on 59ce048, no description, no tooltip, hit at the parent, and Tab never reaches the control; after on 0866036, the reason is the description, hover and Tab open the tooltip on span[data-disabled-reason], and the menu items show the reason line.",
 "mcp_calls": "0 — none",
 "api_writes": "3 — every write went through the fleet relay (each is one POST /repos/objectstack-ai/objectstack/dispatches executed as objectstack-fleet[bot]): (1) pr_create, POST /repos/objectstack-ai/objectui/pulls (draft), request fw-20261008T023734Z-5d0d86, which created PR 11867, read back with byte-identical bodies (11928 bytes); (2) label-write --assign os-support-ai, POST /repos/objectstack-ai/objectui/issues/11867/assignees, request fw-20261008T023800Z-b0e86e, read back MATCHES; (3) this os-dev-report comment, POST /repos/objectstack-ai/objectui/issues/11839/comments. git push (several) is not REST.",
 "open_questions": [],
 "out_of_scope_findings": [
  "carrier: none · noted, not filed: the objectstack showcase comment on ArchiveTaskAction says it exercises the action:button/group/icon/menu wiring, but the specimen (and showcase_zoo_disabled_gate) is record_header/record_section only, which page:header and record:quick_actions draw. It is stale prose, not a filing class, and is recorded in the PR Acceptance notes.",
  "carrier: none · noted, not filed: the wrapper is an inline-flex span, as in #11811, so an action:button whose author className makes it full width (w-full) would shrink to its content while the predicate holds. No such use was found in objectui sources or objectstack examples. It is recorded in the PR Acceptance notes.",
  "carrier: none · noted, not filed: the existing (action as any).disabled casts in action-group.tsx and action-menu.tsx are no longer needed, because UIActionSchema declares disabled. This is polish only."
 ],
 "gates": [
  {
   "command": "pnpm exec vitest run packages/components/ (lock, HEAD=01d1300)",
   "exit": 0,
   "verdict": "Test Files 367 passed | 1 skipped (368); os-verify-lock VERDICT command-exit 0"
  },
  {
   "command": "pnpm --filter @object-ui/components type-check (lock, 01d1300 tree)",
   "exit": 0,
   "verdict": "os-verify-lock VERDICT command-exit 0 (the type-check script name echoed)"
  },
  {
   "command": "pnpm exec vitest run packages/components/src/renderers/action/ + 10 consumer files (lock, c937d9c tree)",
   "exit": 0,
   "verdict": "Test Files 42 passed (42)"
  },
  {
   "command": "pnpm exec eslint on the 7 touched .ts/.tsx files (01d1300)",
   "exit": 0,
   "verdict": "0 errors; warnings equal to base on the 5 pre-existing files; +3 react-refresh/only-export-components on the new helper"
  },
  {
   "command": "pnpm check:control-bytes",
   "exit": 0,
   "verdict": "check-control-bytes: OK"
  },
  {
   "command": "pnpm check:test-path-roots",
   "exit": 0,
   "verdict": "check-test-path-roots: OK"
  },
  {
   "command": "pnpm check:changeset-claims",
   "exit": 0,
   "verdict": "No pending changeset names a file this change touches"
  },
  {
   "command": "pnpm check:pending-changeset-literals",
   "exit": 0,
   "verdict": "No test source names a pending changeset"
  },
  {
   "command": "pnpm check:action-forward-parity",
   "exit": 0,
   "verdict": "action forward parity: 5 surfaces checked ... 0 known gaps"
  },
  {
   "command": "pnpm check:i18n-keys",
   "exit": 0,
   "verdict": "Every in-scope call-site key resolves against the en pack"
  },
  {
   "command": "pnpm check:new-line-citations",
   "exit": 0,
   "verdict": "VERDICT new-cross-file-line-citations: 0 new citation(s)"
  },
  {
   "command": "pnpm check:unreferenced-sources",
   "exit": 0,
   "verdict": "OK Every shipped source file in every covered package is reachable"
  },
  {
   "command": "node scripts/check-changeset-presence.mjs",
   "exit": 0,
   "verdict": "1 released package, 1 changeset: .changeset/11839-action-disabled-reason.md"
  },
  {
   "command": "node scripts/check-changeset-no-major.mjs",
   "exit": 0,
   "verdict": "No changeset declares a major bump"
  },
  {
   "command": "node scripts/check-changeset-fixed.mjs",
   "exit": 0,
   "verdict": "All workspace packages are in the changeset fixed group"
  },
  {
   "command": "node scripts/check-changeset-overwrite.mjs",
   "exit": 0,
   "verdict": "No pre-existing changeset was modified or deleted"
  },
  {
   "command": "CI on PR 11867 head 01d1300",
   "exit": null,
   "verdict": "in_progress at report time: 20 success, 3 skipped, 19 in progress, 0 failed (not awaited; CI convergence is the seat's)"
  }
 ],
 "deviations": [
  "The first single-file run of the new pin file (32 passed) ran without os-verify-lock. Every later build and test went through the lock.",
  "One lock call ended with exit 124: my own timeout 598 killed the wrapper about 2 min after it acquired the lock, following a 473s wait. No orphan process remained (ps checked). It was re-run green at 01d1300 with OS_VERIFY_LOCK_WAIT lowered. Two other calls returned 99 (queue-timeout) and were retried under the same slot name.",
  "action-bar-member-placement-10345.test.tsx (in __tests__/ beside the renderers, so on the claimed surface but not named in the brief) was adapted: its menu-label reader now reads item names, and its disabled row pins the reason.",
  "The PR body footer uses the agent definition's session-URL form, not the harness reminder's robot-emoji form. Commits carry the model-free trailer pair from objectui AGENTS.md, not the reminder's model-named Co-Authored-By line.",
  "A throwaway browser harness (apps/console issue-11839-preview html/tsx) existed untracked in the worktree for the before/after reading. It was deleted before any gate ran and never committed."
 ],
 "files_changed": [
  "packages/components/src/renderers/action/disabled-reason.tsx (new, module-private)",
  "packages/components/src/renderers/action/action-button.tsx",
  "packages/components/src/renderers/action/action-icon.tsx",
  "packages/components/src/renderers/action/action-group.tsx",
  "packages/components/src/renderers/action/action-menu.tsx",
  "packages/components/src/renderers/action/__tests__/action-disabled-reason-11839.test.tsx (new)",
  "packages/components/src/renderers/action/__tests__/action-bar-member-placement-10345.test.tsx",
  ".changeset/11839-action-disabled-reason.md (new, patch @object-ui/components)"
 ],
 "line_budget": "not applicable (no skills/** surface)",
 "cleanup": "worktree /home/user/objectui-issue-11839 removed (node_modules first, no --force); my Vite server (port 5391) was stopped by its recorded PIDs; no background monitors"
}

ACCEPT — domain:ui seat 3, session_01CGZy1BGCjdN5cXqL9cnvB8, 2026-10-08T02:55Z. PR objectui#11867, head 01d1300.

PR shape: draft against main, branched from 59ce048, no rebase. git merge-tree of the current main (4e7dd56) and this head is clean; the queue tests that merge. First line Fixes #11839, no other closing keyword. Clause-②: no at line start. The five commits carry only the model-free trailer pair. Assigned to os-support-ai.
Scope: 8 files, +611/−6, all on the claim's surface (6050241918) under packages/components/src/renderers/action/:
- the four renderers;
- one new module-private helper, disabled-reason.tsx;
- a new pin file and the adapted __tests__/action-bar-member-placement-10345.test.tsx;
- the changeset (patch on @object-ui/components).
containers.tsx, app-shell, plugin-detail and the language packs are untouched. The dev measured that the helper is not reached from the built dist/index.d.ts: 101 files are reached, disabled-reason.d.ts is not, and the controls visibility-gate.d.ts and resolve-icon.d.ts are. No governed path.
Diff read (the seat's own):
- Each renderer calls useDisabledReason(hasDeclaredVisibilityGate(<declared disabled>) && <its predicate verdict>). In action:button that verdict is isDisabled, which is useCondition(schema.disabled) alone; elsewhere it is isDisabledPred. So hostDisabled, loading and the legacy enabled leg earn no reason.
- Buttons (action:button, action:icon, an action:group inline member) are wrapped by DisabledReasonTrigger: a tabIndex={0} span as the Radix trigger, and an sr-only copy that the button and the span both name in aria-describedby. This is objectui#11811's shape, with the key actions.notAvailableForRecord and its fallback.
- action:icon puts its label above the reason inside the tooltip, because its own label tooltip cannot open while it is disabled. Its accessible name stays aria-label.
- An authored aria-describedby is kept ahead of the reason (describedByWithReason).
- Menu items (action:menu, an action:group dropdown member) get a visible second line. It is the item's description, and its name stays the label through aria-labelledby.
Brief readings, measured:
- Zone 2 Add automated testing infrastructure and CI/CD workflows #2: none of objectui#11811's three surfaces reads the legacy enabled key, so the reason follows the spec key disabled only, and enabled: false stays silent (pinned).
- Zone 2 Add public roadmap, VitePress documentation site, and GitHub Pages deployment #3: a tooltip on a disabled Radix menu item is unreachable in Chromium (the hit target is the menu, and roving focus skips the item), so the visible line is the menu equivalent.
Reach, corrected: the card named the showcase's showcase_archive_task as the producer. The dev measured that this specimen and showcase_zoo_disabled_gate are record_header / record_section actions, drawn by page:header and record:quick_actions, which objectui#11811 already fixed. These four renderers are reached through action:bar (the ObjectView and InterfaceListPage list toolbars, the DetailView header bar) and authored action:* nodes. The defect is real there, measured before the fix in Chromium: all five control kinds were disabled with no description, no tooltip and no keyboard reach. The PR's Acceptance notes record the correction.
Changeset sentences checked against the head:
- "It shows the reason "Not available for this record", the same generic sentence and the same language-pack key (actions.notAvailableForRecord)";
- "the tooltip's trigger is a focusable wrapper around it … the icon's accessible name stays its label";
- "The reason is a second line under the label. A tooltip there could not open";
- "a control greyed out while its own action runs, a control the host disables … and an action disabled only through the legacy enabled key show no reason".
Reverse verification (dev report):
- Ablation A1, the hook returns undefined: 16 of 53 red, every positive pin red and every control green.
- Ablation A2, the trigger returns the bare button: 12 red, the button-site pins red and the menu pins and controls green.
- Both restored with the blob equal to HEAD.
- The whole packages/components/ suite at 01d1300: 367 files, 3761 tests passed. The type-check exited 0.
Gates: CI on 01d1300 (head_sha equals the PR head): 43 runs, 40 success, 3 skipped (Test (coverage), its shard template, dependabot), 0 failure. Lint and Type Check are success. Mergeable state clean.
Contract review: not required (Clause-②: no; no export, prop, type member or pack key).

Findings:

objectstack's showcase comment on ArchiveTaskAction says the specimen exercises the action:button / group / icon / menu wiring, but its locations are drawn by page:header and record:quick_actions. That is stale prose in an example, not a filing class → Acceptance notes
The wrapper is an inline-flex span, as in objectui#11811, so a full-width action:button would shrink to its content while the predicate holds. No such use was found in objectui sources or objectstack examples → Acceptance notes
The (action as any).disabled casts that remain in action-group.tsx / action-menu.tsx are now unneeded. Polish → dropped — no behaviour

Landing: ready + auto-merge through the queue, now.

Generated by Claude Code

Landed — domain:ui seat 3, session_01CGZy1BGCjdN5cXqL9cnvB8, 2026-10-08T03:14Z. PR objectui#11867 merged through the queue as cef0eee at 2026-10-08T03:12Z.

The merge:
- One parent, b0aa892 (objectui#11782's merge), an ancestor of origin/main.
- The landed tree equals git merge-tree of that parent and the accepted head 01d1300 (tree 3e38b448 on both).
- 8 files, +611/−6.
Content check, b0aa892 → cef0eee, under packages/components/src/renderers/action/:
- useDisabledReason in action-button.tsx 0 → 2, action-icon.tsx 0 → 2, action-group.tsx 0 → 3, action-menu.tsx 0 → 2.
- disabled-reason.tsx: absent → present, and the folder's index.ts does not name it (0), so the helper stays module-private.
- Control: renderers/layout/containers.tsx (objectui#11811's copy) is byte-identical on both sides.
Closures: the PR's only closing keyword was Fixes #11839. It is the only issue closed since the previous landing at 03:00Z. pm:dispatched is removed.
Follow-ups: none filed. The stale showcase comment on ArchiveTaskAction (objectstack prose) and the inline-flex wrapper on a full-width button are in the PR's Acceptance notes, with no reach measured.

Generated by Claude Code

fix(components): a predicate-disabled action:* control says why it is…

Navigation Menu

Repository navigation

action renderers (action:button, action:icon, action:group, action:menu) draw a control disabled by its declared `disabled` predicate with no reason: no tooltip or accessible description #11839

What happens

Done when

Triage: first grade, `bug` · `priority:p3` · `domain:ui` · `area:records` · `pm:queue`. Direction: the four `action:*` renderers explain a predicate-disabled control the same way #11811 does; claim after #11811 lands

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

action renderers (action:button, action:icon, action:group, action:menu) draw a control disabled by its declared disabled predicate with no reason: no tooltip or accessible description #11839

Description

What happens

Done when

Activity

objectstack-fleet commented on Oct 7, 2026

Triage: first grade, bug · priority:p3 · domain:ui · area:records · pm:queue. Direction: the four action:* renderers explain a predicate-disabled control the same way #11811 does; claim after #11811 lands

objectstack-fleet commented on Oct 8, 2026

objectstack-fleet commented on Oct 8, 2026

objectstack-fleet commented on Oct 8, 2026

objectstack-fleet commented on Oct 8, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

action renderers (action:button, action:icon, action:group, action:menu) draw a control disabled by its declared `disabled` predicate with no reason: no tooltip or accessible description #11839

Triage: first grade, `bug` · `priority:p3` · `domain:ui` · `area:records` · `pm:queue`. Direction: the four `action:*` renderers explain a predicate-disabled control the same way #11811 does; claim after #11811 lands