Main bug display page problems - comment content and formatting
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
New
|
Medium
|
Unassigned |
Bug Description
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
affects /products/malone
done
The page produced by LP when I try to look at the conversation in a
bug report mangles the commenters' formatting and fails to provide
important information about the bug history.
1. Comment text should be displayed in a fixed width font.
2. Comment text should be wrapped, if at all, only so as to fit in the
browser window (ie, only as necessary to avoid horizontal
scrolling). Any wrapping should be visibly marked so that it is
possible to tell, by looking at the screen, where the actual line
boundaries are. (Wordwrap is not necessary but not harmful
provided the above conditions are met.) See my other bug about
page layout.
It is possible that the structure of LP's comment entry system
encourages the submission of comments with paragaphs all run
together into a single line, in which case wordwrap would be
essential. It's difficult to tell by looking at the current
displays.
3. Status changes and comments should be interleaved in the bug
history, and displayed in chronological order; when a single user
action does several things (eg, adds a comment and changes the
status, and/or changes several things at once), the display should
show one action but also appropriately highlight the status
changes. Ie, status changes should use formatting which visually
distinguishes them from running comment text (both for ease of
noticing, and for ease of ignoring). See the Debian BTS for
an example of one way to do this.
4. GPG signatures, extensive mail headers, and other usually
irrelevant information, should be relegated to a subsidiary
`detailed history' or `uninteresting guff' page. In general, all
metadata such as incoming email headers will either (a) be normally
interesting and should therefore be presented in a structed manner
in the LP page layout proper or (b) be normally uninteresting and
should therefore be suppressed in the usual view.
5. The full headers and text of incoming emails should be available on
request. As a pair of litmus tests, the full detailed view should
be useable (a) to reverify the GPG signature on an incoming mail
and also (b) to help diagnose mail routing problems and delays by
detailed analysis of headers such as Received chains.
6. The repetition of the bug title at the top of each comments is
superfluous. Furthermore, it serves to distract the eye from the
fact that the grey box does contain some often-useful information
such as the author and date of a comment.
Ian.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.6 <http://
iD8DBQFD1k+
tcxlPA2curxIcqb
=Ookz
-----END PGP SIGNATURE-----
I've made a note of this report in the description of bug 3002, because I think this report contains some good ideas.