Comment 3 for bug 540312
Revision history for this message
| Lesmana Zimmer (lesmana) wrote Re: always redirect to absolute url for bug | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
ok. thank you for explaining the the idea behind the many urls.
i didn't know that the heat is context dependent. i think, since it is context dependent, it should go in the context dependent section of the page, by that i mean the "affects table". the page trail (that thing directly beneath the bug title) is also context dependent, it should also go in the "affects table".
the "affects table" is already crammed enough as it is now. but i find it very confusing to have some context dependent information *inside* the table, and some context dependent information (heat, trail) *outside* of the table. maybe it is time to redesign the table, perhaps with some information hidden until the user clicks on an expand button for a specific row.
another thing, about the direct urls to the comments. these two links point to the same comment:
https:/
https:/
the first links show the comment in the context of the hundredpapercuts project. here the context makes sense (the comment states that the bug is not in the hundredpapercuts project). the second link, however, shows that comment in the context of the gedit bug. if i landed on that comment by that link i will find it very confusing. why should someone talk about the hundredpapercuts project in a gedit bug?
curiously, this link leads to an error page: https:/
question: by what rules is the context chosen if one uses the short url? is it always the original context it was reported in?
yet another thing, about this url:
https:/
it lands on a page which i think i can call contextless, with a confusing title (bug #xxx is not in ubuntu). what about that?
i think i have to split this bug up, if you maintain the position for the many context dependent urls.