Missing "read more" link for large truncated comments
Bug #2027799 reported by
Andreas Hasenack
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
When a bug commend is deemed to large to be displayed in full, launchpad offers a "download full text" link at the begginning, an used to show a "Read more" link at the bottom.
The difference between the two is that the "Download" link does exactly that, downloads a text file, and the "Read more" link allowed you to read the full comment in the browser.
The "Read more" link seems to be gone, at least from the bugs I have been interacting with. An example is comment #13 of https:/
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: bugs ui |
To post a comment you must log in.
Heh, I missed Andreas's bug. I opened a question with very similar thoughts:
Hello, there was a discussion in ~launchpad [1] about the limits of characters for when a comment will receive the "download full text" link and when a comment will receive the "view full comment" (or similar text) link.
I can completely understand why launchpad won't render the entire contents of large comments in a bug view. I can sort of understand why launchpad won't render the entire contents of a very large comment on the individual comment view page, but the current limit feels pretty low.
I think each comment header should have three buttons:
- one to download the comment
- one to view the comment in a 'styled' view on a page of its own
- one to view the comment in a 'raw' view (delivered as text/plain)
(I use https:/ /addons. mozilla. org/en- US/firefox/ addon/open- in-browser/ so that viewing download links is much less painful, but probably most people don't even know this is an option.)
Viewing comments in the browser is usually more convenient than needing to use external programs. Offering even a 'raw' view without the pretty styling / html escaping / etc is a step up in convenience. (It would even be useful for short comments that include copy-and-paste of terminal output! How often have you seen useless ls or zpool status or tree output, because the html output crunched all the spaces and tabs?)
Thanks
[1]: https:/ /chat.canonical .com/canonical/ pl/6znwzukrm7nf zgro96i14b3g6r