Still one thing buggy with the new editor

[mendel_leisk]

<p>I've noticed if I have double-spaces between paragraphs, to create a definitive gap, and then edit my posting in the brief window you're allowed to do that, those gaps are lost. Doesn't seem to be possible to get them back.</p>

[MichaelChang]

<p>Mendel, just add a manual carriage return after every sentence in the post edit box and you'll get it back. Annoying but workable.</p>

[mendel_leisk]

<p>Doesn't work in the situation I describe above: extra carriage returns are stripped out, existing or new.</p>

[mendel_leisk]

<p>To clarify: if I post a response with double carriage returns, then decide to edit it in the 10 minute or so window you have after posting, the dc's are stripped out.</p>

[MichaelChang]

<p>It worked for me, at least I thought it did. Let me check with a few carriage returns.</p>

<p>Edited test line with 5 carriage returns.......</p>

[MichaelChang]

<p>Well it appears you get a double carriage return limit even if you edit with more than 2 carriage returns.</p>

[joshroot]

<p>Yes, that is to keep people from making long blank posts with one word and the beginning and end. There really are very few legit reasons why you would need to have 4-5 [cr] in a row.</p>

[Norma Desmond]

<p>Josh--</p>

<p>Makes sense. But the original point still remains. If you have just one line space between paragraphs in your original post and then go to edit even just a part of it in the 20-minute editor, even though the line spaces still show in the preview mode, they get stripped out in the actual posting. You actually have to go back and add a second line space to each paragraph in order to get that one space to appear in the edited version.</p>

[joshroot]

<p>Nevermind, I see what you are saying.</p>

[twmeyer]

<p>Yup, this has been buggin me lately, too. The old <p> worked so well. Now it seems useless as are plain ole carraige returns (there's an archaic term for you). If it can catch caps and cussin, it seems like excessive empty lines wouldn't be much more elusive. Good luck and thanks... t</p>

[joshroot]

<blockquote>

<p>Yup, this has been buggin me lately, too. The old<br /> worked so well.</p>

</blockquote>

<p>That is a matter of opinion. The "old way" worked well if you knew circa 1999 HTML or understood that there was no way to have a single [cr] without it. Frequently we got long posts from people that did know that single [cr]'s wouldn't work and then you just get a huge block of unformatted text.</p>

<p>Single [cr]'s and double [cr]'s work just fine now. They just have different spacing in the text editor than they do in the display. But for anyone who is confused, hey, that's why we have the "confirm/update" page. Look at your post. If it isn't the way you want it, then fix it.</p>

[joshroot]

<p>Also, the problem that Mendel brings up should be fixed now.</p>

[Norma Desmond]

<p>Here's a test of Mendel's problem.</p>

<p>Here's a edit the word test of Mendel's problem.</p>

<p>Yes. It's now fixed. Thanks. Great stuff.</p>

<p> </p>