It looks like you're new here. If you want to get involved, click one of these buttons!
JuliusBorisov wrote: »
Should we maybe probably possibly try the Rich Editor again? They seem to have updated it: https://open.vanillaforums.com/discussion/37360/vanilla-3-0-is-now-available-updated-3-0-2
Ok, I have enabled it for an experiment and reverted back.
Well, this seems bad on multiple levels, i vote to return to BBCode, even if the white background issue can be solved.
-no preview (but i can't find a way to use codes, so that's maybe relate with that)
-no editable quotes
-i found the spoiler function, but can not use it well. Can't write a new paragraph outside it if activated once, and i don't find it by editing a comment.
Edit: ok with double enter i can escape from the spoiler tag, and i can copy it to paste in an older comment, but it's far from convenient.
'Tis something most unnatural here and I want no part of it
Automation is the bane of humanity and will be the ultimate cause of its downfall. Thus, for the sake of the human race, I vote for the use of a BBCode based text editor, like it was in the very beginning before Vanilla started to create this new WYSIWYG text editor. It is a serious burden to sane online existence, and thus must be replaced with the old, stable manually-formattable, fully functional, and easier to use manual text editor. Vanilla, please let us use that good old text editor that used HTML.
This is why Martians are more advanced than us. They use manual text editors.
@JuliusBorisov My first impression: The new rich editor is not very intuitive to use, and it takes time to properly format comments. Direction keys (especially up/down) behave in a very unintuitive way.
I think a detailed instruction guide is really needed or there will be many frustrated users.
Testing: bold, italic, strikethrough, code and links. No underlined text? No colored text?
Emojis: 🤔 🐹 😱 👽️
Testing advanced features:
(no 1st level heading)
Quoting a quote...
// A script block
Tab key doesn't work (bad for writing code) :(
Testing markdown codes...
bold, italic, code
Nothing to see here...
This is code inside a spoiler...
(or should be inside a spoiler)
Edit: Code inside spoilers doesn't work???
The worst part of this IMO, is that the editor truncates quotes. So if there was a long string of quotes in a post, and you try to quote it, you only get a portion of the text near the top, and the later posts, which are probably what you're replying to are now lost.
Also, I notice that quotes are no longer collapsed in any posts, even those that predate the change.
They work, but only when the formatting is through the button to the left, and only if the tabs are pasted in. They are lost when formatting through the dropdown menu by highlighting the text, which also only appears to work on single lines, selecting multiple lines doesn't always present the dropdown menu for text. I don't know why there is a small white box underneath this paragraph, there are no lines after it.
JuliusBorisov wrote: »
Now the background when using Rich Editor is black. What is your opinion - would it still be bad to switch to it?