New editor does not do proper paragraph breaks without [Rich Editor] option

The new editor has a pretty substantial bug.  If the user leaves the editor in the new "default" (plain text) format, it does not respect carriage returns.  It should do so.  Most particularly, it really ought to follow the convention that two carriage returns correspond to a paragraph break.

sort by: active | newest | oldest
1-10 of 13Next »
I like the rich editor as default.
Is their a way to do that?
Re-design7 years ago
It's pretty discouraging to write and format a long answer just to have to REFORMAT it because you forgot to load the rich editor.
kelseymh (author)  Re-design7 years ago
You don't have to tell me! I am quite disappointed that these issues have not been fixed. Supposedly staff is equally irritated. The most obvious fix, rolling back to the previous editor until a proper "plain text" editor can be validated, seems to be somehow either impossible or ignored :-(
kelseymh (author) 7 years ago

Bump. There have been a number of independent postings complaining about this bug. We've also had some discussion of it in e-mail. It is an extremely counter-intuitive behaviour, and ought to be straightforward to fix (revert to the Rich Editor default, but with the buttons hidden).

There are a bunch of knock-on bugs as a consequence of this change, when you switch into the Rich Editor with text already in place. All of those would vanish trivially with the above implementation.

Ah, good, so it's not just me. Also, clicking "Next" on the comments has no effect anymore it seems.
kelseymh (author)  Javin0077 years ago
That's a separate bug, which you can find reports about by searching (use a Google advanced search like "inurl:Next" and "inurl:community" to limit results to forum topic titles). However, that bug was fixed a week or two ago, supposedly. Could you try deleting your recent history (cache) and try again?
Agreed, it's really annoying. :(
kelseymh (author)  Jayefuu_test7 years ago
Why did you choose "_test" as the suffix, rather than "_bugs"?
Kryptonite7 years ago
testing... /test
1-10 of 13Next »