This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 1012183 - [ja_JP][User Portal] Basic tab -> right details pane layout issue with a long OS name
[ja_JP][User Portal] Basic tab -> right details pane layout issue with a long...
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-userportal (Show other bugs)
3.3.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: nobody nobody
Pavel Stehlik
: i18n
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-25 19:08 EDT by Yuko Katabami
Modified: 2013-09-25 19:14 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-09-25 19:14:29 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Yuko Katabami 2013-09-25 19:08:22 EDT
Description of problem:
When the name of operating system is long (e.g. Red Hat Enterprise Linux 6.x.x64), it does not fit in the provided space and it moves to the next line, which make the layout messed.


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


How reproducible: 100%


Steps to Reproduce:
1. Login to User Portal with ja-JP selected
2. Open Basic tab
3. Select a VM which has OS "Red Hat Enterprise Linux 6.x.x64"
3. Check right side details pane.

Actual results:
"Red Hat Enterprise Linux 6.x.x64" does not fit in the space provided. It is placed line below, which is too close to the next line (xxGB)

Expected results: 
"Red Hat Enterprise Linux 6.x.x64" should be aligned with "Operating System"


Additional info:
Comment 1 Yuko Katabami 2013-09-25 19:14:29 EDT
I am sorry, I realized that the layout is fixed when I extend the browser window to a sufficient width.
Closing this bug now.

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