You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2023. It is now read-only.
Originally suggested by @fdupont-redhat for the Target Namespace field of the plan wizard as part of https://bugzilla.redhat.com/show_bug.cgi?id=1929731. We decided we should only do this if we do it consistently everywhere.
A basic implementation was done in f80c692 that I am reverting. We could revisit that and abstract it out into lib-ui as some kind of component like TextWithSubstringHighlight. Also, that implementation is case-sensitive, ideally we could highlight results even if they don't match the case of the search term (not an issue for k8s resources though since they cannot contain capital letters).
The text was updated successfully, but these errors were encountered:
mturley
changed the title
Add highlighting of search terms in text-based filters throughout the UI
Add highlighting of partially-matched search terms in text-based filters throughout the UI
Feb 18, 2021
mturley
changed the title
Add highlighting of partially-matched search terms in text-based filters throughout the UI
[BZ#1951023] Add highlighting of partially-matched search terms in text-based filters throughout the UI
May 11, 2021
https://bugzilla.redhat.com/show_bug.cgi?id=1951023
Originally suggested by @fdupont-redhat for the Target Namespace field of the plan wizard as part of https://bugzilla.redhat.com/show_bug.cgi?id=1929731. We decided we should only do this if we do it consistently everywhere.
A basic implementation was done in f80c692 that I am reverting. We could revisit that and abstract it out into lib-ui as some kind of component like
TextWithSubstringHighlight. Also, that implementation is case-sensitive, ideally we could highlight results even if they don't match the case of the search term (not an issue for k8s resources though since they cannot contain capital letters).The text was updated successfully, but these errors were encountered: