Bug 815261 - The delete app button should be in the right place on app/console/applications page
Summary: The delete app button should be in the right place on app/console/application...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ---
: ---
Assignee: Fabiano Franz
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-23 08:39 UTC by Yujie Zhang
Modified: 2015-05-15 01:08 UTC (History)
2 users (show)

Fixed In Version: rhc-site-0.91.7-1+
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-27 20:46:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot1 (159.20 KB, image/png)
2012-04-23 08:39 UTC, Yujie Zhang
no flags Details
screenshot2 (92.57 KB, image/png)
2012-04-24 07:17 UTC, Yujie Zhang
no flags Details

Description Yujie Zhang 2012-04-23 08:39:34 UTC
Created attachment 579451 [details]
screenshot1

Description of problem:

The delete button on app/console/applications/$appname should be in the right side of the form.

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

devenv_1736

How reproducible:always


Steps to Reproduce:
1.Go to openshift website
2.Go to app/console/applications/$appname pages
3.
  
Actual results:

The delete button on app/console/applications/$appname is not in the right place.Details see in attachment.

Expected results:

The delete button should be in the right side of the form.

Additional info:

Comment 1 Yujie Zhang 2012-04-24 07:17:19 UTC
This issue will also cause display error,details see in attachment, so change the priority to high.

Comment 2 Yujie Zhang 2012-04-24 07:17:38 UTC
Created attachment 579765 [details]
screenshot2

Comment 3 Fabiano Franz 2012-04-24 19:43:44 UTC
Fixed.

Comment 4 Yujie Zhang 2012-04-25 08:22:40 UTC
(In reply to comment #3)
Verify this bug on devenv_1741, it has been fixed now, thanks.


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