Bug 1291521 - Long project name is out of boarder in confirm message when deleting project from web console
Summary: Long project name is out of boarder in confirm message when deleting project ...
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: Robb Hamilton
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-15 03:29 UTC by Yadan Pei
Modified: 2016-05-12 17:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-12 17:08:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
DeleteProject (52.23 KB, image/png)
2015-12-15 03:29 UTC, Yadan Pei 		no flags Details
View All

Description Yadan Pei 2015-12-15 03:29:58 UTC 
Created attachment 1105829 [details]
DeleteProject

Description of problem:
Create a long name project without 'Display Name',when delete this project on web /console page, project name in prompt message is displayed out of boarder

Version-Release number of selected component (if applicable):
openshift v1.1-442-gde31d75
kubernetes v1.1.0-origin-1107-g4c8e6f4
etcd 2.1.2


How reproducible:
Always

Steps to Reproduce:
1.Create a project with 63 characters(longest value) like 012345678901234567890123456789012345678901234567890123456789012 
2.Delete this project by clicking delete button on /console page 

Actual results:
2.Clicking the delete button will prompt message for users to confirm their deletion, project name is out of boarder, refer to attachment

Expected results:
2. project name should be displayed well 

Additional info:
Comment 1 Robb Hamilton 2016-03-09 15:51:52 UTC 
https://github.com/openshift/origin/pull/7890
Comment 2 Yadan Pei 2016-03-14 01:01:14 UTC 
tested against devenv-rhel7_3705 with Firefox 44, Chrome 46, Safari 9, IE 11, Edge 25, works well, so move to VERIFIED
Comment 3 Yadan Pei 2016-03-14 01:54:41 UTC 
Update Chrome version to 49, checked on Chrome 49, works well
Note You need to log in before you can comment on or make changes to this bug.