The Rich Text Editor is woefully in need of some essential functionality bug fixing

Since beginning to use Joplin recently this year, I've become familiar with fighting with the Rich Text Editor on a regular basis. There are some core interactions with it that are surprisingly overlooked and I'm surprised haven't been addressed or reported already.

I recently filed several formatting bugs that I am running into daily:

(I have several more I need to document and file, but this is the first free moment I've had in awhile to sit down and write things up)

I've kind of gotten the feeling the Rich Text Editor, despite being a fresh feature addition in the recent years, has not had the crucial full polish pass it needs to be a baseline functional component. Asides from bug reports, is there ANYTHING I can do to help with this?

Please note I am not interested in plugins to awkwardly patch and workaround these issues, these are clearly core Joplin bugs that need fixing.

Wow!

I had no idea there were this many things wrong.

I primarily add text and edit in the Markdown editor because I have plugins that I've added that only work in the Markdown editor. They don't work in the rich text editor. Using the rich text editor for me doesn't let me use the plugins, essentially, and do what I want to do. I've never come across, and probably would never come across, any of these bugs that you've documented here.

I do hope they get looked at and fixed.

I will be monitoring this thread.

:zany_face::nerd_face:

The first 4 of those issues I don't think are issues in the ProseMirror editor which mobile uses. The plan is at some point to enable it on the desktop app too, but I'm not sure about the timeline for this. For #17011, it doesn't look like the ProseMirror editor currently supports a heading on a checkbox item, but possibly that's not supported by the markdown spec. For #17012 this behaviour varies on different apps to be honest, many apps will replace the text in this scenario, so I'd consider indentation here a feature rather than a bug

That's valid and still fairly up for debate. I personally feel it's become a standard in modern UX and it should indent. This discourse post editor I'm typing in right now even supports it. It's a contemporary UX feature certainly but it's a nice one to have.

The proper heroic solution, of course, is to make it a configurable setting in options.

(This ironically brings up a another bug I just noticed in Rich Text Editor in that the indenting functionality, in general, does not actually seem to do anything or even be supported)

I should also add, that the Joplin Markdown editor supports selecting text and indenting, so thus it creates an inconsistent UX expectation which is closer to being a bug than a feature, imo.