Bug 1805730 - Route Editor: Not enough padding between Target Port and Security form groups
Summary: Route Editor: Not enough padding between Target Port and Security form groups
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.5.0
Assignee: Robb Hamilton
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-21 12:57 UTC by Samuel Padgett
Modified: 2020-07-13 17:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Version: 4.4.0-0.ci-2020-02-20-044240 Cluster ID: 223e19ec-0f8c-499c-9e99-dcb9fa4ed59f Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:73.0) Gecko/20100101 Firefox/73.0
Last Closed: 2020-07-13 17:16:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Not enough padding (115.39 KB, image/png)
2020-02-21 12:57 UTC, Samuel Padgett
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 4410 0 None closed Bug 1805730: Fix spacing, semantics of Create Route form 2020-09-18 08:33:57 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:17:19 UTC

Description Samuel Padgett 2020-02-21 12:57:31 UTC
Created attachment 1664718 [details]
Not enough padding

Minor layout issue, see screenshot. The "Target port for traffic." text is too close to the "Security" label.

Comment 3 Yanping Zhang 2020-03-04 09:36:57 UTC
Checked on 4.5 cluster with payload 4.5.0-0.ci-2020-03-03-053944.
Check on the route creation page, now the space is reasonable between "Target port for traffic." text and the "Security" label.

Comment 5 errata-xmlrpc 2020-07-13 17:16:59 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.