Bug 1329551

Summary: autocomplete of operators and values on content hosts page shows (e.g.) ">" instead of ">" in drop-down menu
Product: Red Hat Satellite Reporter: Jan Hutař <jhutar>
Component: Content ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bkearney
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-12 21:34:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
too escaped operators
none
too escaped values none

Description Jan Hutař 2016-04-22 08:42:08 UTC 
Description of problem:
On content hosts page, when operators or values are autocompleted for "last_checkin", ">" is shown as "&gt;" in the drop-down menu.


Version-Release number of selected component (if applicable):
satellite-6.2.0-8.2.beta.el7sat.noarch


How reproducible:
always


Steps to Reproduce:
1. Go to Hosts -> Content Hosts
2. Type this into search box and wait for drop-down menu appears:
   "last_checkin "
3. Also try to type following and wait for what drop-down menu shows:
   "last_checkin > "


Actual results:
See screenshot.


Expected results:
Special chars should be displayed correctly there.
Comment 1 Jan Hutař 2016-04-22 08:42:47 UTC 
Created attachment 1149679 [details]
too escaped operators
Comment 2 Jan Hutař 2016-04-22 08:43:10 UTC 
Created attachment 1149680 [details]
too escaped values
Comment 4 Bryan Kearney 2016-07-26 15:25:24 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 5 Bryan Kearney 2016-07-26 15:29:29 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 7 Bryan Kearney 2017-01-12 21:34:34 UTC 
I am no longer seeing this on 6.2.6. Closing this out. If you are still seeing this issue, please feel free to re-open with additional information.