finding(fields): FieldEditWidget declares the whole DOM pass-through block but forwards only `autoFocus` — a host's `onBlur` / `onFocus` / `id` / `name` / `tabIndex` silently never reach the control

[claude]

Found while measuring objectui#6859. Filed rather than folded in: it is a different
defect class from that card (which is about the data table's commit path), and it sits
one layer ABOVE the widgets rather than in them.

What

packages/fields/src/FieldEditWidget.tsx declares its props as
FieldWidgetComponentProps (generic over any). That type is the controlled-input keys
intersected with FieldWidgetDomProps, AriaAttributes, and an open data- family, so
a caller may pass id, name, autoFocus, tabIndex, onBlur, onFocus, onClick,
any aria- and any data- attribute with no type error at all.

The component body then destructures { field, value, onChange, readonly, autoFocus }
and renders the resolved widget with exactly those five plus compact. Everything
else is silently dropped. Only autoFocus survives out of the whole DOM pass-through
block, and its doc comment explains why it in particular was forwarded — which reads
like an incomplete pass-through rather than a designed narrowing.

Why this is the repo's own first-class class

This is the @object-ui/fields DECLARED-BUT-NOT-DELIVERED shape, named as first-class
in packages/fields/src/widgets/toDomProps.ts — "a key that type-checks, reads as
supported, and silently never reaches the element" (objectui#3290's aria-required,
objectui#3222's validation slot). The compile-time assertions in that file bind the
widget contract to the whitelist in both directions. Nothing binds THIS factory to
either.

The measurement that makes it concrete

Counted over EDIT_WIDGETS for objectui#6859: all 27 components the map resolves to
already deliver the host's DOM set to a real control — 26 call toDomProps themselves,
UserField delegates its whole props object to LookupField. None of them strips
onBlur.

So the widgets are not the gap; this factory is. Concretely: the data table's
renderCellEditor seam could never hand an injected cell editor an onBlur, however
willing the widget, because a host handler cannot get past this destructure.

Hosts to weigh before grading: ObjectGrid.renderCellEditor (packages/plugin-grid),
InlineFieldInput (packages/plugin-detail), RequiredFieldsDialog
(packages/plugin-kanban). Whether any passes one of these keys today is the triage
question; the compiler currently says all of them may.

Directions (not a proposal to widen anything)

1. Forward the declared block — declared = enforced, the direction toDomProps itself
   takes. The widgets already whitelist what may reach the DOM, so the factory would be
   passing through, not reopening a spread.
2. Or narrow this component's declared prop type to the five keys it actually honours,
   so passing the others becomes a compile error instead of a silent drop.

Either closes it; the first matches how the rest of the package resolved the same
question. Unassigned and ungraded on purpose — filed by the objectui#6859 seat.

Generated by Claude Code

---

Generated by Claude Code

[zhuangjianguo]

Triage (objectstack skills seat, cross-lane finding round): p2 · pm:queue · domain:ui. The repo's own named first-class defect class (declared-but-not-delivered, toDomProps' charter), measured precisely: 27/27 widgets deliver, the factory alone drops the declared DOM block, and concrete hosts are named. Dispatch note: direction 1 (forward the declared block — declared = enforced) matches how the package already resolved this question; direction 2 is the fallback if a measured host depends on the drop. The dispatched dev should first measure whether any of the three named hosts passes the dropped keys today — that decides p1-escalation vs plain repair.

---

Generated by Claude Code

[claude]

Claiming this card.

• session: session_013hfmP9hoMd3dJwTh85J4yB
• branch: claude/issue-6909-fieldeditwidget-passthrough
• base: a5a799d63ef1f6dedfac3729aa647e4e02b7e427 (origin/main at branch time)
• direction: 1 only (forward the declared DOM pass-through block). Direction 2 (narrowing the published prop type) is explicitly out of scope for this claim.
• worktree: objectui-6909

Files expected in scope: packages/fields/src/FieldEditWidget.tsx plus its test file. Assignee field is owned by the dispatching PM; I do not write it.

Generated by Claude Code

---

Generated by Claude Code

[claude]

Claim amendment (same session, same round) — the declared file surface widened by one file.

• session: session_013hfmP9hoMd3dJwTh85J4yB
• branch: claude/issue-6909-fieldeditwidget-passthrough
• PR: fix(fields): FieldEditWidget forwards the DOM pass-through block it declares #7009 (draft)

Original claim named packages/fields/src/FieldEditWidget.tsx plus its test. Added:

• packages/components/src/renderers/complex/data-table.tsx — comment only, no code. Its injected-editor comment justified the document-level pointerdown listener partly with "FieldEditWidget forwards autoFocus and nothing else out of the DOM block, so a host handler could not reach the control through it even if one were passed". This change makes that sentence false, so it is corrected in the same commit rather than left to rot. The listener stays load-bearing on the untouched half of the same reason (the renderCellEditor context object still has nowhere to put an onBlur). Evidence and the exact wording are in the PR body.

Full file surface of this branch: packages/fields/src/FieldEditWidget.tsx, packages/fields/src/__tests__/FieldEditWidget.domPassThrough-6909.test.tsx, packages/components/src/renderers/complex/data-table.tsx, .changeset/6909-fieldeditwidget-dom-pass-through.md.

Generated by Claude Code

---

Generated by Claude Code