Bug 988140 - Vibe4.0.2:Incorrect chars are displayed in Responsibilities field of user's profile
Summary: Vibe4.0.2:Incorrect chars are displayed in Responsibilities field of user's p...
Status: VERIFIED FIXED
Alias: None
Product: Vibe
Classification: Micro Focus Vibe
Component: UI - User Profile (show other bugs)
Version: 4.0.2
Hardware: x86-64 Windows Server 2012 R2
: P1 - Urgent : Normal
Target Milestone: 4.0.2
Assignee: David Lewis
QA Contact: Ira Messenger
URL:
Whiteboard:
Keywords: CCB, Functionality
Depends on:
Blocks:
 
Reported: 2016-07-08 07:07 UTC by Anna Wang
Modified: 2016-08-03 14:59 UTC (History)
3 users (show)

See Also:
Found By: i18n Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
20160706_profile_responsibilities (35.69 KB, image/gif)
2016-07-08 07:07 UTC, Anna Wang
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Anna Wang 2016-07-08 07:07:59 UTC
Created attachment 683465 [details]
20160706_profile_responsibilities

Server : Windows2012 R2 
Build  : novell-vibe-4.0.2-windows_20160702193924
Client : Windows 7 64bit/IE 11

Steps to Reproduce:
01.Log in to Vibe "http://vibe_hostname" as a user;
02.Edit user's profile;
03.In the "Responsibilities" section,input some chars then set font size
   and text color;
04.Click OK button,then view profile.

Actual Result:
Please see screenshot.Some incorrect chars are displayed in
"Responsibilities" field. 

Expected Results:
It should be displayed normally.
Comment 1 David Lewis 2016-08-01 19:52:15 UTC
For security reasons, I recently changed the profile fields to be displayed as raw text by default, instead of as HTML.  As part of that change, I also incorrectly changed the Responsibilities field too.  I've changed it back to being rendered as HTML (all other fields are still raw text).  This is okay from a security perspective because we are sanitizing the HTML to ensure that users can't inject unsafe HTML.
Comment 2 Novell Build 2016-08-02 02:57:11 UTC
This fix is in the Vibe OnPrem 4.0.2 build 20160801193939.  open source project revision 23580, and closed source project revision 8083.
Comment 3 Ira Messenger 2016-08-03 14:59:36 UTC
Verified Vibe_OnPrem/enterprise/proton/20160802193926