Community
Participate
Working Groups
upon opening existing tasks, tasks with long descriptions get wrapped differently in 3.4.1 causing false incoming.
Filed bug against bugzilla.org: https://bugzilla.mozilla.org/show_bug.cgi?id=509152
Created attachment 145035 [details] patch as posted on bugzilla.mozilla.org
*** Bug 288157 has been marked as a duplicate of this bug. ***
see comment #67 bug 25699, observe how Mylyn bug hyperlinking is broken because there is a hard line wrap between the word 'bug' and the bug number 290469 This line wrapping also causes description text and comments to render incorrectly. It is very anoying, especially for stack traces which often occupy almost double the required vertical space (see bug 290436 for an example) Any progress on this one?
(In reply to comment #5) > see comment #67 bug 25699, Oops, I meant bug 256699 comment #67
Hi David I just attached a new patch to the related Mozilla bug (https://bugzilla.mozilla.org/show_bug.cgi?id=509152), Marc Schumann, who I think is in charge of that part of Bugzilla commented on the bug and will hopefully find time to test the patch. The line break in the URL is unfortunate, but I do not think we can do anything about that on Mylyn, there seems to be no way to tell if a line break is intentional or caused by Bugzilla. Eclipse.org wont apply the patch until Bugzilla approved it (which makes a lot of sense, given that it might break things I am not aware of), so it seems we are stuck for now with the line breaks.
Thomas, thanks for the update! It seems to me that this issue affects any client accessing the API. Hopefully the Bugzilla team will see it as an important issue. Yes, I agree that the fix has to happen on the server.
The fix has been applied. Looks like it will make it into the next non-security-patch release.
Great!
The fix has been absorbed into Bugzilla 3.4.2.
Has eclipse.org updated (or do they have any plans to update to) 3.4.2?
(In reply to comment #11) > The fix has been absorbed into Bugzilla 3.4.2. 3.4.3 :)
*** Bug 295093 has been marked as a duplicate of this bug. ***