Description of problem: This behavior has been really irritating me (and others) for years. When I carefully enter text in the Description box which approaches the end of the line, and then click on submit bug, the result often appears with some words wrapped and dangling on the next line. This ruins the nice formating that I took time to create. It would be wonderful if I could use the full line, but at least bz could always wrap the words while I'm editing so I can make adjustments. The latest example to illustrate can be seen in bug 605313 comment 5 with the dangling "state)", which was not dangling when I submitted the bug. I'm going to enter the same text here that I did in that bug. Right now as I edit this the "state)" is not wrapped. (I wonder of the appearance/ disappearance of the scroll bar at the right has anything to do with it.) I'm going to click submit bug and we'll see if "state)" is wrapped. 1276717591 fenced:default conf 5 1 0 memb 4 5 6 7 8 join 8 left (starting state) 1276717625 fenced:default conf 4 0 1 memb 5 6 7 8 join left 4 (-4, partition) 1276717626 fenced:default conf 5 1 0 memb 4 5 6 7 8 join 4 left (+4, merge)
Yep, it was wrapped again. What makes it even more absurd: look at all that empty white space to the right of the text above which it won't use.
(My apologies if this is a browser bug, which I now realize may be the case.)
Hi, Can you do me a favor and try your testing on our development server to see if the next version of Bugzilla does this as well? We are hoping to roll out the new version in next couple months and I would like to see if it also has the same problem. https://bz-web2-test.devel.redhat.com Should be your same username/password and email is disabled so feel free to make any changes you like. Thanks Dave
Entered bug 601775 on devel server, results are the same.
Another irritating example, I just wrote https://bugzilla.redhat.com/show_bug.cgi?id=633567#c45 and it wrapped "panic," to the next line. It appeared at the end of the previous line before I saved, of course.
It's cathartic to post examples here :-) Here's another great example: https://bugzilla.redhat.com/show_bug.cgi?id=604139#c108
Testing a theory that "quoting" text with ">" can override the wrapping. > 1276717591 fenced:default conf 5 1 0 memb 4 5 6 7 8 join 8 left (starting state) > 1276717625 fenced:default conf 4 0 1 memb 5 6 7 8 join left 4 (-4, partition) > 1276717626 fenced:default conf 5 1 0 memb 4 5 6 7 8 join 4 left (+4, merge)
Wow, it looks like that did it! Now I just need a way to automatically "quote" everything I paste into a bugzilla text box.
Ditto, this is annoying for me too. Please fix it!
This still really infuriates me on a regular basis. See https://bugzilla.redhat.com/show_bug.cgi?id=663397#c32 where the word "that" got pushed to the next line, making the text look like crap. Any idea when this could be fixed?
As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time. If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically. Thanks, the Bugzilla team.
As noted previously, the Bugzilla Team is cleaning up a large number of outstanding issues that have bit rotted. This bug is being closed as there has been no response to that notification. If you believe this bug is still important please reopen this bug in the NEW status and PM will consider it.
For years bz would forcibly line wrap, and the only way to sanely paste debug info was to use ">" at the start of the line. Then a few months ago it would never line wrap, and now it's forcibly line wrapping again but without the ability to use > to paste debug info. This makes it impossible to use bz for debug logs. Note that the comments above which demonstrated using > to avoid line wrapping are now wrapped. Is bugzilla meant to be used for software debugging any more or only for management purposes?
*** This bug has been marked as a duplicate of bug 965911 ***