I’ve been a happy user of the Markdown editor in micro.blog, but it seems to have been replaced by something… else? It’s super-weird and I’m not happy about it.
At least allow people to opt in or out of it! Was this tested on real users?
@manton mentioned a new editor on core int but didn’t think it was ready for release and I never use the web one so I don’t know what it presented like before.
FYI to make use of the b, i and link buttons you have to have text selected as it is wrapping the markdown automatically for you, its not switching you into b or i mode like it would in a word editor. I know some of this from my own approaches to a “rich” markdown editor, the active and wrap is the simplest approach but as you have shown is is not obvious. What I did and looking now at discourses editor the buttons are always usable and when tapped they add in dummy text strong text and highlight the dummy text for you to quickly write over.
example of text injected when tapping b button
**strong text**
As regards the quotations it has changed the way this was handled before from what I can tell, so that only by including a space will it give you a line break but this then stylistically puts in a “paragraph” break and doesn’t continue the quote, so you get all those extra gaps in your post, it should handle it like this using the > between paragraphs to create a line break but stay in quote style like this
first quote of thing you want to say
second part of the quote from same author strong text
example of markdown
>first quote of thing you want to say
>
>second part of the quote from same author strong text
If manton can tweak the editor to these approaches I think it will improve the UX
1 Like
Trying to write HTML as a person who knows how to write HTML is quite possibly one of the most frustrating things I have ever tried to do in this new editor. Every new character typed puts your cursor one character back from where you expect to be so you literally cannot just write HTML fluently anymore.
1 Like
I’ve just fixed a couple issues, including not being able to type some HTML tags. More improvements coming.
2 Likes
Thanks, looks like it’s solved the formatting issues, but it’s still behaving strangely in terms of jumping about.
I’m happy to help test things before you deploy next time!
It is better but there is some jumping around still. For example, it doesn’t seem to expect the author to create both an opening and closing HTML tag at the same time so if I do that my cursor ends up in the wrong place afterwards.
I’ve updated the editor to address all of the known HTML tag issues. The cursor shouldn’t jump around anymore just when editing HTML tags and attributes.
1 Like