Comment 11 for bug 2627
Revision history for this message
| Stuart Bishop (stub) wrote Re: Bug comment and description whitespacing being munched yet again | #11 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
2eb648a
demo site
(Get the code!)
The use cases would be:
Fred enters some text in a bug comment form. He submits the form and
sees his comment exactly as he entered it.
Fred replies to a Malone bug mail. The next day he visits the bug page
and sees his comments exactly as he entered them.
ASCII art is a good demonstration and test - we cannot predict what users are going to enter. We can only predict that users will be pissed if they spend 20 mins creating an ASCII art diagram and Malone does not display it correctly. We can also predict that if we can't render the cow and bunny correctly we can't render other data that people might consider more legitimate correctly, such as stack traces, tracebacks, arbitrary terminal cut & paste.
If we cannot meet these generic use cases until we move to CSS3, then perhaps we can work around the issue. Two options I can think of are:
- Sniff browser, and use proprietary CSS or HTML hacks to display
things correctly.
- Provide a link in the bug comment subject and next to the bug
description that lets you view the raw text.