Bug 1804991 - incorrect border for groups matching filter in topology
Summary: incorrect border for groups matching filter in topology
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.5.0
Assignee: cvogt
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks: 1804994
TreeView+ depends on / blocked
 
Reported: 2020-02-20 03:30 UTC by cvogt
Modified: 2020-07-13 17:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1804994 (view as bug list)
Environment:
Last Closed: 2020-07-13 17:16:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 4361 0 None closed Bug 1804991: show solid border for topology shapes matching name filter 2020-06-23 08:38:18 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:16:49 UTC

Description cvogt 2020-02-20 03:30:27 UTC
Description of problem:
Knative service, helm group, and operator backed groups have a dashed border. Even when the node name matches the filter, the dashed border remained and changed to orange.

According to the designs, the border should be solid when matching the filter text.

How reproducible:


Steps to Reproduce:
1. deploy a knative service to your namespace
2. go to developer console -> topology
3. enter filter text in the top right input field

Actual results:
Border of knative service is a dashed orange line.


Expected results:
Border of knative service is a solid orange line.

Comment 3 Gajanan More 2020-03-06 08:38:48 UTC
I have validated this bug on:
Build: 4.5.0-0.ci-2020-03-05-232742
Browser: Google Chrome Version 78.0.3904.108
Marking this as verified.

Comment 5 errata-xmlrpc 2020-07-13 17:16:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409


Note You need to log in before you can comment on or make changes to this bug.