Bug 800611
Summary: | Use of … (html horizontal ellipsis) breaks render in some messaging UIs | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Trevor McKay <tmckay> |
Component: | cumin | Assignee: | grid-maint-list <grid-maint-list> |
Status: | CLOSED WONTFIX | QA Contact: | MRG Quality Engineering <mrgqe-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | Development | CC: | croberts, esammons, matt, mkudlej, sgraf |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | cumin-0.1.5492-1 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-26 20:06:30 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Trevor McKay
2012-03-06 19:16:17 UTC
For some reason, the value of the form field was being set to a <span> tag, which is not valid XHTML. My solution was to avoid adding the unnecessary <span> tag when rendering the shortened text in the form field. Fixed in revision 5435 on trunk. Reproduced on cumin-0.1.5444-3 Long queue generates: --- This page contains the following errors: error on line 35 at column 28: Unescaped '<' not allowed in attributes values Below is a rendering of the page up to the first error. --- Tested on cumin-0.1.5675-1 queue - qmfagent-047b2251-db2d-45f5-90e2-826cccafb293 shows in 'Add binding' widget - qmfagent-047b2251-db2d-45f5-90e2-826…b293 The queue name should be properly displayed in the input box. Submitting binding says: Add binding: Failed ('ascii' codec can't decode byte 0xe2 in position 36: ordinal not in range(128)) Shouldn't queue name field in 'Add binding' widet be non-editable? --> ASSIGNED MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs. |