Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1575949 - [ko_KR] [VM Portal] Messages option text "No messages" not proper.
Summary: [ko_KR] [VM Portal] Messages option text "No messages" not proper.
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.UserPortal
Version: 4.2.3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-08 11:28 UTC by Pooja Yadav
Modified: 2018-05-09 07:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-09 07:14:56 UTC
oVirt Team: Virt


Attachments (Terms of Use)
Message option not proper (17.52 KB, image/png)
2018-05-08 11:28 UTC, Pooja Yadav
no flags Details

Description Pooja Yadav 2018-05-08 11:28:54 UTC
Created attachment 1433158 [details]
Message option not proper

Description of problem: On VM portal home page, on the top right corner when we click on messages option, and if there are no messages, the no messages text doesn't appear properly, its broken.
Please refer attachment

Version-Release number of selected component (if applicable):
Version 4.2.3.4-0.1.el7

How reproducible:
Always

Steps to Reproduce:
1. Launch VM Portal with ko_KR locale
2. Click on the messages option on top right corner


Actual results:
"No messages" text does not appear properly

Expected results:
"No messages" text should be proper.

Additional info:

Comment 1 Michal Skrivanek 2018-05-09 07:14:56 UTC
this is a wrong tracker for upstream ovirt-web-ui. Copied to https://github.com/oVirt/ovirt-web-ui/issues/594


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