Harvester Dashboard and the Rancher UI Library: Backporting Accessible Comboboxes to React 17

Where the two codebases meet

Harvester's web dashboard is built on the Rancher Dashboard framework, so its form controls inherit the Rancher UI component library. In the 1.3.x series, the storage-class and network selectors in the VM-create wizard are custom dropdowns with reported keyboard and screen-reader gaps, while the library's newer accessible select/combobox primitives reportedly require React 18 — and Harvester's dashboard has stayed on React 17.

That frames an integration decision at the boundary between the two projects: backport the newer primitives into Harvester's React 17 codebase, or wait for the planned React 18 migration in a future Harvester release and accept the delay.

Constraints: Harvester tracks Rancher Dashboard releases closely, so a fork-level React bump risks upstream drift. Harvester's CI reportedly has no automated accessibility gate to catch regressions on either path, and theme overrides can reintroduce contrast failures that better primitives alone will not address.

Version assumptions here reflect the 1.3.x line and should be confirmed against the current dashboard repository before triage.

Open questions

• Are the newer Combobox/Select primitives importable in Harvester's current React 17 build, or do they depend on React 18 APIs?
• Would a compatibility shim preserve the keyboard-focus and live-region behavior, or only approximate the markup?
• Has upstream's React 18 migration progressed far enough that waiting is now the lower-risk path?