| Summary: | Remarks don't render in UI rendered pane at all | ||
|---|---|---|---|
| Product: | [Community] PressGang CCMS | Reporter: | mmurray |
| Component: | Web-UI | Assignee: | Matthew Casperson <mcaspers> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.1 | CC: | cbredesen, lnewson, mcaspers |
| Target Milestone: | --- | ||
| Target Release: | 1.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-10-17 23:44:31 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: | |
|
Description
mmurray
2013-10-15 02:54:26 UTC
Fixed in 201310170811 This can be tested in PressGang Next. The rendered view now has a checkbox that can be used to display remarks. The setting will be remembered for each topic. Going to move this back to assigned on usability grounds. The checkbox is on the same line as the condition, so if the condition tex or content spec name is large the checkbox disappears from the screen. There is no scroll bar to be able to move over and select the checkbox, so I believe we should just place it on a new row below the condition listbox. Also tested this out in an incognito window and the <remark> text never displayed. The only thing that change was the title lost it's numbering (ie "1. Enabling USB Redirection in Windows" became "Enabling USB Redirection in Windows"). Note: The specific example is from Topic 7386 Fixed the rendering in Chrome. Added the remarks option to a second line for smaller rendered views. Verified that it now works in Firefox and Chrome. It's also worth noting that users might have to clean their cache to see the change (I had to do that in Chrome). Clearing Cache is definitely required. It wasn't working for me before I cleared it. |