524795 - Regression: Bad wrapping

Status: RESOLVED DUPLICATE of bug 436189

(Bugzilla :: Creating/Changing Bugs, defect)

Description

[Ben Bucksch (:BenB)]

See bug 524698 comment 0 and comment 8. Some lines are wrapped just before the end of line, and then again, leaving only one word per line. I may have used backspace, but as far as I know, the lines were "flowing" in the input field, I entered no hard line breaks are the points where they wrapped.

It looks like bugzilla hard-wraps the comments at a certain line length, and then at display time (e.g. in HTML) applies another wrapping with a shorter line length.

This is a regression, I haven't seen that before.

Actually, I have seen that years ago for a short time, and it was a bugzilla bug back then.

Comment 1

[Ben Bucksch (:BenB)]

Nice. The comment above is an example of the bug itself. I'll now, for testing, just keep typing here, I will not use the return key, I will not even use Backspace, to see whether bad line wrapping appears here as well, just to prove that it's bugzilla.

Comment 2

[Ben Bucksch (:BenB)]

Attachment: Screenshot

Apparently, this is dependent on the font size. I have "monospace" 12 as Monospace font in the FF font dialog, on SuSE Linux. If I increase or decrease the font size in Firefox using Ctrl+mouse wheel, the bad wrapping is gone.

This strongly suggests that this is a limit on the width in the HTML, plus hard wrapping on the server side.

Just remove the width from the HTML.

Comment 3

[Ben Bucksch (:BenB)]

> This is a regression

I'm not so sure about that anymore. I may also have changed by font size unintentionally using Ctrl-mouse wheel.

Still the fixed width in HTML should be removed. Either hard wrap on the server, or let the browser wrap, but not both, as that will lead to exactly these problems.

Comment 5

[Max Kanat-Alexander]

(In reply to comment #3)
> Still the fixed width in HTML should be removed. Either hard wrap on the
> server, or let the browser wrap, but not both, as that will lead to exactly
> these problems.

  Unfortunately, in order to do that, I'd need one of the following features:

  1) A working standard Unicode wrapping algorithm implemented in Perl.
  2) The ability for CSS to wrap at an exact number of characters.

Comment 6

[Ben Bucksch (:BenB)]

Well, using *both* then makes it even worse, for the same reasons.