Bug 1388446 - [userinterface_public_691] The place of X button for the first build-secret in BC editor page is not good
Summary: [userinterface_public_691] The place of X button for the first build-secret i...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Management Console
Version: 3.x
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Jakub Hadvig
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-25 11:42 UTC by Xingxing Xia
Modified: 2016-12-09 21:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-09 21:51:21 UTC
Target Upstream Version:

Attachments (Terms of Use)
X button in Build Secrets (11.57 KB, image/png)
2016-10-25 11:42 UTC, Xingxing Xia 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Xingxing Xia 2016-10-25 11:42:42 UTC 
Created attachment 1213879 [details]
X button in Build Secrets

Description of problem:
The place of X button for the first build-secret in BC editor page is not good. See attachment

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Jakub Hadvig 2016-10-31 10:01:54 UTC 
In progress PR https://github.com/openshift/origin-web-console/pull/735
Comment 2 openshift-github-bot 2016-11-01 19:31:15 UTC 
Commit pushed to master at https://github.com/openshift/origin-web-console

https://github.com/openshift/origin-web-console/commit/9daa7bd47ccf1cee674ecfb6745a6f90f2b8058a
Bug 1388446 - Refactor osc-secret and osc-source-secret style
Comment 3 Xingxing Xia 2016-11-02 10:31:38 UTC 
Verified with openshift v1.4.0-alpha.0+90d8c62-1000 (devenv-centos7_5294).
Firefox now displays the 1st X button near secret selection box with good alignment.
Also did a regression test using other browsers (Chrome, Edge), they still displays well.
Thank you!
Note You need to log in before you can comment on or make changes to this bug.