fix: handle keyboard shortcut for text filter

[CodyWMitchell]

Handle keyboard shortcut for text filter

• Pressing / will focus the text filter

OCPBUGS-63391

[patternfly-build]

Preview: https://react-data-view-pr-data-view-594.surge.sh

A11y report: https://react-data-view-pr-data-view-594-a11y.surge.sh

[nicolethoen]

since this component attaches a window-level event listener, consuming applications don't currently have a way to opt out of this behavior.

This could be problematic in scenarios where:

1. The application wants to manage keyboard shortcuts at a higher level (e.g.,
   in a centralized keyboard handler)
2. Multiple DataViewTextFilter instances exist on the same page, causing
   multiple listeners to fire
3. The / shortcut conflicts with existing application shortcuts

Could we consider an optional prop in case they want more fine tuned control over this feature?

export interface DataViewTextFilterProps extends SearchInputProps {
  // ... existing props
  /** Enable keyboard shortcut (/) to focus the filter. Defaults to true. */
  enableShortcut?: boolean;
}

[github-actions]

🎉 This PR is included in version 6.4.0-prerelease.13 🎉

The release is available on:

• GitHub release
• npm package (@prerelease dist-tag)

Your semantic-release bot 📦🚀

[rhamilto]

Thanks for the enhacement! This works as expected. However, I fear discoverability is nil. In OpenShift console, we used to include a badge in the input with a shortcut hint. I think we'll want something similar here so users know what the shortcut is.

GitHub has similar functionality.

Screen.Recording.2026-03-16.at.10.22.43.AM.mov

Can we add something similar?

[rhamilto]

Hmm. It occurs to me we can and probably should use our existing TextFilter instead of DataViewTextFilter since this code already exists and is what we were using.

[rhamilto]

Hmm. It occurs to me we can and probably should use our existing TextFilter instead of DataViewTextFilter since this code already exists and is what we were using.

See openshift/console#16151