Are you sure the patch will work?

We do wordwrap() in some cases too.. (which actually has a different bug, the 
preview page and the final text do not wrap in the same way.

Ah, I see.

Allowing for wider textareas, only partially fixes the problem.

I don't know the solution here but I'd say that wrapping should be done soft/virtual in the browser and that's it. No wrapping at any other stage. At least not in code. Hopefully the browser will wrap the text under it's normal rules.

When displayed, don't use <pre>, except for the "Test script", "Expected Result" and "Actual Result". And no wrapping.

The next issue comes from emails. I still think that the wrapping here should be handled by the reader.



When it comes to emailing, I'm not sure. Do any of the modern readers automatically wrap long lines?


OOI. Using the JS Console for Google Chrome, I set this textarea's wrap property to virtual - it was physical. Virtual SHOULD mean that only the line breaks I manually put in will be transmitted. The others, for example, the one that exists BEFORE the word "that" won't be present.

We'll see when I press submit.

Based upon that, the virtual setting seemed to work. Only MY line breaks were transmitted. And the <pre> block for the comment uses CSS styling to wrap, so no additional line breaks were introduced.

You can see that is the case if you cut and paste the output into a text editor. The 14 lines of text (ignoring blank lines) present would be pasted as 8 lines. Just as I typed them in.

The email I got for that also has no wrapping except where my reader (GMail) needs to put them in.

So. If LOOKS like using wrap="virtual" could be enough.

The manual page is not available now --> this ticket may be closed.

This issue is not particularly related to a certain documentation
page, burt rather a general issue.  However, the "Report a bug"
links target Github issues for a while now, so I think we can
close this ticket.