>>Works well when it was sent and is read back from your server. When ansering Al's example with long pre-tag, preview of answered text with pre-tag inculded needed some scrolling (in FF), but the end result after "send" was much fine. Nothing big and much better then otherway around, but beats the benefit of preview somewhat...
>
>That could be. That is why we always recommend members to cut the PRE code area lines to avoid such long lines. Even in the code, I adjust all my lines to fit a certain width we all agreed on, dev team for examples, so when switching projects we have the same similar environment. For me, it just wouldn't make sense, and it making it extremely difficult to read a test where the width would be 2000 pixels wide.

Similar here - unless it is something like a line of SDF copied in as a template.

>Same thing with a newspaper. There are reasons why there are columns in there. So, when I have a project opened, I also pay attention to use line continuation. So, when I paste it in here, it is already ready to be paste and appear pretty much ok in here as is.

As said, works fine after preview. If a quick glance at the code shows no easy to fix oversight, I'd probably check max(linelen[pre-area]) and give out a warning message that preview might be affected and reccommend shorter lines inside pre-tags. We are programmers here, so we will understand...