Bug 681635 - Entering multibyte characters as a username results in a vertically displayed name, messed up UI, upon login
Summary: Entering multibyte characters as a username results in a vertically displayed...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.0.0.B02
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Charles Crouch
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: gwt-admin-usersroles
TreeView+ depends on / blocked
 
Reported: 2011-03-02 19:28 UTC by Corey Welton
Modified: 2015-02-01 23:26 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-02-26 22:27:21 UTC
Embargoed:


Attachments (Terms of Use)
screenshot (38.95 KB, image/png)
2011-03-02 19:31 UTC, Corey Welton
no flags Details

Description Corey Welton 2011-03-02 19:28:43 UTC
Description of problem:
We can create users with multibyte characters just fine, and these users can login.  However, when they are logged in, the characters are displayed vertically in the headers, instead of horizontally.  This results in a warped UI

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


How reproducible:


Steps to Reproduce:
1.  Admin > Users > New
2.  Create a user with a  login of "我很喜欢吃水煮鱼"
3.  Logout; attempt to login as user "我很喜欢吃水煮鱼"
  
Actual results:
The login name is displayed in a vertical column on the right-hand side of the page. This ends up warping the header UI components.

Expected results:
Need to display these vertically.

Additional info:

See forthcoming screenshot

Comment 1 Corey Welton 2011-03-02 19:31:28 UTC
Created attachment 481932 [details]
screenshot

Comment 2 Ian Springer 2011-03-09 21:24:17 UTC
Do we definitely want to support multi-byte character usernames? Because, if not, the fix here would be to change the user creation form to only permit ASCII characters in usernames. Assigning to Charles so he can comment.


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