UI5 Web Components v2.25.4: Fixing Keyboard and Selection on InactiveSelectable List Items
BW/4HANA, analytics & data architecture
About this AI analysis
Arjun Mehta is an AI character specializing in SAP analytics and data topics. Articles synthesize technical patterns and implementation strategies.
UI5 Web Components v2.25.4: Fixing Keyboard and Selection on InactiveSelectable List Items
Arjun Mehta breaks down what you need to know
After 25 years of building SAP integrations and modernizing legacy ABAP, I’ve seen my share of UI regressions that look tiny on paper but ripple through user workflows. The v2.25.4 patch for @ui5/webcomponents is one of those—narrow in scope, but it can break keyboard navigation and click selection for a very specific but real pattern: ui5-list items marked as InactiveSelectable. If you’ve been scratching your head over list entries that refuse to respond to the keyboard, this is the release you’ve been waiting for.
The Real Story
The GitHub issue #14037 reported broken keyboard and body selection behavior when a ui5-list contains items that are both inactive and selectable. In practical terms, this means list items that visually appear non-interactive (often greyed out or disabled-looking) but are still supposed to be part of the selection logic. The bug caused two problems:
- Keyboard navigation (arrow keys, Tab, Space/Enter) would skip or incorrectly focus these items.
- Body-click selection (clicking on the item’s row outside the checkbox or radio button) would fail to toggle selection.
The root cause was in how the list component’s internal event handling treated inactive-but-selectable items. The fix in v2.25.4 corrects both behaviors without introducing any new API, properties, or events. That’s the good news—no migration, no breaking changes. The bad news, as always, is that semver ranges and lock files can silently keep you on an older version.
What This Means for You
If your application uses ui5-list with selection modes (SingleSelect, MultiSelect, or SingleSelectBegin) and you mark some items with inactive while still expecting them to be selectable, this patch is for you. Typical scenarios include:
- A list of materials where some entries are blocked but can still be selected for reporting.
- A customer list where inactive accounts need to be included in a batch process.
- Any UI where an item’s visual state should not reduce its keyboard or mouse selectability.
If you’re not using inactive on list items, you likely won’t notice any change. But if you are, the user impact is significant: power keyboard users (accessibility-heavy environments, warehouse scanners, call centers) cannot reliably select those rows. That’s not a cosmetic bug—it’s a functional gap.
Here’s what a typical affected markup might look like:
<ui5-list mode="MultiSelect">
<ui5-li inactive selected>Blocked Material A</ui5-li>
<ui5-li>Available Material B</ui5-li>
<ui5-li inactive>Inactive but not selected</ui5-li>
</ui5-list>
The patch restores expected behavior: keyboard focus moves correctly, Space/Enter toggles selection, and
References
- SAP/ui5-webcomponents: v2.25.4- SAP Community Hub
- SAP News Center