When I make a comment on a bugzilla bug page, the automatic linebreaks that bugzilla inserts in my comment don't seem to take bugzilla-generated text into account. (e.g. the "[details]" that gets added when I link to a comment) e.g. consider this block of text, with an attachment link in the middle: a b c a b c a b c a b c a b c a b c a b c a b c a b c a b c a b c a b c a b c a b c a b c a b c a b c a b c attachment 1 [details] [diff] [review] a b c a b c a b c a b c a b c a b c a b c a b c a b c a b c a b c a b c a b c a b c a b c

(In reply to comment #0) > e.g. consider this block of text, with an attachment link in the middle: > > a b c ... I didn't put any line breaks in that block of text -- the ones there are those "intelligently" added by Bugzilla. In particular, the second line's linebreak seems to have been placed without taking the [details] string into account. That line should break a few characters earlier. In its current state, the second line is too long, and the "c a" string at the end get pushed to its own orphan line. This looks broken.

Here's a screenshot of what I see on comment 0. (just in case the bug isn't visible with other OS's / font settings / etc)

(In reply to comment #0) > (e.g. the "[details]" that gets added when I link to a comment) If it's not clear, I meant to say "when I link to an *attachment*" here.

V.Duplicate