[david-rios-uipath]

This PR fixes two main issues:

1. Variable action buttons now show when focused on the list item

Before	After

2. TabPanel was a focusable element without a purpose

Before	After

It addresses the referenced ticket. The tab panel element being focusable just bothered me for a long time.

[github-actions]

Dependency License Review

• ✅ 1957 package(s) scanned
• ✅ No license issues found
• ⚠️ 2 package(s) excluded (see details below)

License distribution

License	Packages
MIT	1721
ISC	91
Apache-2.0	57
BSD-3-Clause	28
BSD-2-Clause	23
BlueOak-1.0.0	8
MPL-2.0	4
CC0-1.0	4
MIT-0	3
MIT OR Apache-2.0	2
(MIT OR Apache-2.0)	2
Unlicense	2
LGPL-3.0-or-later	1
Python-2.0	1
CC-BY-4.0	1
(MPL-2.0 OR Apache-2.0)	1
Unknown	1
Artistic-2.0	1
(WTFPL OR MIT)	1
(BSD-2-Clause OR MIT OR Apache-2.0)	1
CC-BY-3.0	1
0BSD	1
(MIT OR CC0-1.0)	1
MIT AND ISC	1

Excluded packages

Package	Version	License	Reason
@img/sharp-libvips-linux-x64	1.3.4	LGPL-3.0-or-later	LGPL pre-built binary, not linked
khroma	2.1.0	Unknown	MIT per GitHub repo, missing license field in package.json

[Copilot]

🟡 Changes recommended

NodeIOView needs keyboard focus targets for its read-only JSON fallback and empty Schema states.

2 open issues

• Make empty JSON tree states keyboard focusable · New
• Make fallback JSON pre focusable when panel has no JSON view · New

What changed in this PR

This PR adjusts keyboard navigation in Apollo’s side-panel tabs and makes JSON tree row actions visible while their row contains focus.

Changes:

• Removes default panel tab stops in PanelTabsContent and NodeIOView’s Schema and JSON panels.
• Preserves MetadataForm’s focusable text-only empty states.
• Adds focus-within visibility for JSON row actions and related regression assertions.

File	Description
packages/​apollo-wind/​src/​components/​ui/​panel-tabs.tsx	Defaults panel content to tabIndex={-1} and documents the override.
packages/​apollo-wind/​src/​components/​ui/​panel-tabs.test.tsx	Tests that Tab skips panel content by default.
packages/​apollo-wind/​src/​components/​ui/​json-tree-view/​RowActions.tsx	Reveals actions when their row contains focus.
packages/​apollo-wind/​src/​components/​ui/​json-tree-view/​JsonTree.test.tsx	Checks hover and focus-within reveal classes.
packages/​apollo-wind/​src/​components/​forms/​metadata-form.tsx	Keeps text-only empty-state panels focusable.
packages/​apollo-react/​src/​canvas/​components/​NodeIOView/​NodeIOView.tsx	Removes tab stops from Schema and JSON panels.

_{Review effort: Balanced}

[github-actions]

Storybook visual diff

⚠️ Visual changes detected: 17 changed (of 544 compared, 527 unchanged). View report

Baseline is the deployed main Storybook, so changes merged to main after this branch was last updated can also appear here. Logs

Updated (PT): Oct 22, 2026, 12:16:30 PM

[github-actions]

📊 Coverage + size by package

Per-package coverage and bundle size on this PR. New-line coverage = of the source lines this PR adds or changes, the % hit by tests.

Package	Coverage	New-line coverage	Packed (gzip)	Unpacked	vs main
@uipath/apollo-core	—	—	42.02 MB	50.17 MB	±0
@uipath/apollo-react	58.0%	— (12 untracked)	8.14 MB	32.17 MB	+73 B
@uipath/apollo-ui-icons	—	—	2.86 MB	6.97 MB	±0
@uipath/apollo-vertex	—	—	—	—	—
@uipath/apollo-wind	79.4%	100.0% (1/1)	810.7 KB	4.68 MB	+138 B
@uipath/ap-chat	85.8%	—	40.42 MB	45.71 MB	±0

_{"Coverage" is each package's own coverage.include scope (e.g. apollo-core instruments only scripts/). "Packed"/"Unpacked" come from npm pack --dry-run and only cover built packages — "—" means not measured this run (package not affected / not built). "vs main" is the packed (gzipped) delta against the last successful main build (the package-sizes artifact from the Release workflow); "—" there means no main baseline was available this run. The baseline is main's latest build, not this PR's exact merge-base, so it includes any drift since the branch diverged. Packages with no vitest config are omitted.}

[Copilot]

🟡 Changes recommended

Disabled tabbed forms and variable-panel no-results states still lose their fallback keyboard focus targets.

2 open issues

• Disabled populated forms lack a focusable panel tab stop · New
• No-results state lacks a focusable keyboard target · New

2 resolved since last review

• Make fallback JSON pre focusable when panel has no JSON view
• Make empty JSON tree states keyboard focusable

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Tabs containing only rule-disabled fields still lose the fallback focus target needed for keyboard scrolling.

1 open issue

• Preserve panel tab stop when rules disable all descendant fields · New

2 resolved since last review

• No-results state lacks a focusable keyboard target
• Disabled populated forms lack a focusable panel tab stop

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

The focused changes have regression coverage and no unresolved blocking findings, with the remaining Safari limitation explicitly accepted.

No open issues 🎉

1 resolved since last review

• Preserve panel tab stop when rules disable all descendant fields

_{Review effort: Balanced}