Closed
Bug 313713
Opened 20 years ago
Closed 19 years ago
User-Agent and Build ID lines now wrapped and hard to read
Categories
(Bugzilla :: Creating/Changing Bugs, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: alqahira, Unassigned)
References
Details
(Keywords: regression)
I don't know if this is possible or needs to be a general Bugzilla enhancement instead, or....
The User-Agent and Build Identifier lines (on reports from Bugzilla Helper) are now wrapped, and the most important parts (the actual version number and build date) are now the "in-between" lines of a four-line, "heavy-looking" stack. I find it harder to read and pick out those bits of data now.
I've noticed that some long lines (URLs) aren't wrapped; is it possible to special-case the UA and Build ID lines not to force-wrap, too?
Updated•19 years ago
|
Assignee: justdave → justdave
Comment 1•19 years ago
|
||
Moving this to the Bugzilla product to get some more eyes on it. It's possible we already have some hack to tell the templates not to wrap a line, if so I can just modify the comment template. But I'm not aware of it, and I guess this is a good reason to add one if we don't have one.
Assignee: justdave → create-and-change
Status: UNCONFIRMED → NEW
Component: Bugzilla: Other b.m.o Issues → Creating/Changing Bugs
Ever confirmed: true
OS: Mac OS X 10.2 → All
Product: mozilla.org → Bugzilla
QA Contact: myk → default-qa
Hardware: Macintosh → All
Version: other → 2.20
Updated•19 years ago
|
Keywords: regression
![]() |
||
Comment 2•19 years ago
|
||
Currently, replies are not wrapped, i.e. lines beginning with ">". If you want to permit the UA and Build ID to remain as is, you have to hack Bugzilla::Util::wrap_comment().
justdave, I would tend to say that this should remain a hack for b.m.o, and not be implemented in our code.
Comment 3•19 years ago
|
||
I think we may just have to live with this. Looks like people have done for the past year, anyway.
Gerv
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•