Implemented all of the above to-do list, the editor should now match what will actually be rendered even more closely, yay! Still not 100% sure about 4, would appreciate testing feedback: is it better now, or before when shift enter exited the code block and enter added a new line?
Also, forgot to mention this above, but the editor should (almost entirely) support pasting formatted content from Google Docs. I'm on Linux so haven't tested with Word.
In terms of future development, I'm hoping to put in a language selector for code blocks, which would just be an input that pops up when you click on an arrow in the code block. Shouldn't be THAT difficult I think. Open to ideas for other improvements.
@admiralarjun you replied just as I was about to post this, answers below:
admiralarjun will be great if users can check and uncheck them in static pages
Hmm, so having modes where on posts, only the author could check/uncheck (and that would update the database), and in static pages, allowing anyone to check/uncheck, but not updating the database? Having it be configurable per-post would be quite challenging, since there'd need to be a way for authors to indicate the mode. And that either means an extra field in the composer (quite complex), or some weird bbcode that isn't rendered (not self explanatory).
admiralarjun will be great if we can change the "details" to any text of choice in the spoiler option.
Unfortunately this is a limitation of the text formatting library we use. An external extension could override that, but I don't think it's something I'll be doing.
admiralarjun cursor not appearing in the blank area after inserting the code block.
That's not the case for me. Could you record a video of your screen when this happens?