I just wanted to come back here to say how appreciative I am for this extension. For a tech related community I can see the regular markdown editor being preferred, but for pretty much any other type of community it’s much easier for your average user to see the formatting as they type.

I also haven’t noticed my site loading any slower. It seems just as fast to me. And so the size of this extension doesn’t seem to hurt.

Thank you for making this!

I’ve run into an interesting situation. The original editor uses <br> tags in between lines. This worked best when posting something like poetry.

This rich text editor instead starts a new paragraph each time enter/return is pressed.

What this means is, when posting poetry, I’ve gone from:

the first line
the next line

to:

the first line

the next line

Using CSS to change the spacing won’t work out because then posts won’t have any spacing. Even in between "real" paragraphs.

I think this is a common problem with wysiwyg editors. Some even advertise that you can switch between auto p and br due to this type of scenario.

Does this editor have a way to go from auto p on enter to br?

    010101 Would it be preferable for paragraphs to be separated by 1 newline instead of 2 newlines? Right now, one newline is possible via shift-enter. That's behavior that could be changed though, either as an admin setting or globally.

      i have an issue with rich text.

      if i start a new post by quote a text from a post? i need to toggle off preview in composer to start writing off the quote tag, after that, i can start writing on a new line, and toggle ON again rich text

      here the sample:

      @askvortsov

        Hari haha ... i some times hit "esc" instead of enter

        impossible that i'm thinking all exept this!!!!!!!!!! feel so stupid right now

        • [deleted]

        What is replacement fot Shift + Enter on mobile for WXSIWYG / Rich Text Editor?

          [deleted] What is replacement fot Shift + Enter on mobile for WXSIWYG / Rich Text Editor?

          I don't think there is one. I'm very open to suggestions of how that functionality can be otherwise achieved though. Outside of 1-line-separated paragraphs, any other major usage?

            • [deleted]

            askvortsov I'm very open to suggestions of how that functionality

            I really do not know... It is not a necessary feature at all.

            Like many other extensions, I think this one will just depend on the type of community whether it’s worth it or not. Not just due to size but functionality. And this is something I’ve experienced with many other wysiwyg editors. There’s many positives and negatives, so you just have to decide what’s worth it and what’s not worth it.

            For a poetry forum I have I’m going back to the standard editor. Because I need that single line type of experience... regular line breaks versus paragraphs for every line return. But, I also use Flarum for my personal blog. There, this extension will work great. Because there I’m writing standard paragraphs.

            I can see why this was never part of core from the beginning. Because there’s so many variables and preferences.

            One more FYI for a future release. Inserting links isn’t working for me on mobile.

            I still think this extension is amazing and I thank @askvortsov for creating it. Again, depending on the community, this was needed.

              • [deleted]

              • Edited

              For what it's worth, TinyMCE had and still has the same issues... My personal preference is the current editor with Markdown.

              v1.1.0

              • Added a preference configurable in the settings page to disable separating paragraphs by an extra blank line. This should accomplish what you're looking for. 010101
              • Fixed inserting link when that's the first thing done after opening the composer
              • Dropdowns on Safari don't work when the keyboard is open. Added a workaround by displaying dropdown content in a modal. 010101

                askvortsov

                Nice! Works great, thank you! I think I’ll use this at my poetry forum now after all.

                The only remaining thing I don’t love is how quoting works as mentioned above. But, I know there’s no simple solution. Will a user realize they need to hit enter a couple times? Maybe. Maybe not. But, without this editor will they know markdown? Probably not. So either way, you'll have users potentially not quite understanding something. And, you've already gone above and beyond by making this so I can live with quotes as-is (for now). 🙂

                Perhaps I'm missing something, but what's the problem with automatically adding a new line when quoting? That's how the composer work without this editor after all.