Bug #5896
rendering problem with angle brackets in issue tracker
| Status: | Rejected | Start date: | 01/14/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Zach Leslie |
% Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Affected Puppet version: | Branch: | |||
| Keywords: | ||||
| Votes: | 0 |
Description
When I submitted issue #3692, the last sentence looked like this:
“check that the configuration version is at least [left angle bracket]N[right angle bracket], to be sure that you have the latest changes to [left angle bracket]filename[right angle bracket]”.
Now, it looks like this:
“check that the configuration version is at least [blank], to be sure that you have the latest changes to [blank]”.
Apparently, something in the whatever-to-html converter has changed from displaying things in angle brackets, to not displaying them. Please change it back.
I’d suggest that recognised markup elements like “>” at the beginning of a line, or “<pre> … </pre>”, should be interpreted according to the markup rules, but anything not recognised as valid markup should be displayed, not hidden.
History
Updated by Alan Barrett over 1 year ago
Viewing the source of the HTML page shows that it contains “[less than]N[greater than]”, where it should contain “[ampersand]lt;N[ampersand]gt;”. Hiding of unrecognised markup is being done by the web browser. The problem on the server side is failure to escape the characters that have special meaning in HTML.
Updated by James Turnbull over 1 year ago
- Status changed from Unreviewed to Investigating
- Assignee set to Zach Leslie
Updated by Zach Leslie about 1 year ago
>>><<< testing < the magic > of pipes
Updated by Zach Leslie about 1 year ago
- Status changed from Investigating to Rejected
It seemed to work fine in the last update I made. I can’t speak on what happend in the ticket you mentioned, but this looks to br working just fine. I also just filed a ticket recently where I used angle brackets in the text and had no issue.