Javascript editors trying to reinvent desktop paradigms but without the 40-odd years of practice and having all the events arrive whenever they feel like is one of the most frequent irritations of web-based platforms for me, because you use a text editor so frequently and therefore encounter its problems similarly often.
For example, earlier today I was editing a small internal app in Retool. I typed something, instinctively went for Cmd-Z, and it reverts a bunch of changes I made in the query I had open 5 minutes ago. Of course, by the time I spot it and hit Shift-Cmd-Z, the internal state has updated so now it redoes some other unrelated undo operation and I have two broken things to fix.
And then of course there's Notion, the champion of "you've hit a keyboard shortcut and it's applied it to something halfway across the screen from the selection, or possibly just given up trying to do anything useful and deleted a few paragraphs of text at random". Perhaps they were pining for the outrageously janky experience that was attempting to make even the most innocuous of formatting changes in earlier versions of Word For Windows.
If I accidentally fat-fingered e.g. the \ key at the end of a message ("Got it!\"), I want to
1. press the up key
2. press backspace
3. press enter
to delete the last character in the last sent message.
But unless you actually wait at least a second after step 1, the UI is so sluggish in starting the edit of your last message that you instead get "please type a message to continue" because you pressed enter while the New Message text box still had focus.
Things are much worse if you want to do anything more complex. Say, capitalize the first letter of the last sent message (up, home, delete, type capital letter, enter). Usually results in complete gibberish, like appending the capital letter to the message, or sending it in a new message (depending on how fast you are).
That's what that was! I experienced this behavior for years writing posts or comments on facebooks mobile site, helped me a lot to wean myself of that one.
Yes! I had something like that and it was so frustrating I wrote a post (on FB, sigh) about it, looks like it was August 10.
I had written a comment with multiple paragraphs (which I guess they don't expect people to do, or test for) and I wanted to add something to the next-to-last paragraph, and when I tried to type "matters" it would keep locking me in autocomplete tagging for friends name "Matthew", and as soon as I dismissed the cursor would leap to the end of the comment. If I tried to click back, the cursor kept jumping to the end!
Users who don't wish to learn markdown can simply spend two seconds hovering over a "Markdown guide" tooltip at the bottom of the textarea whenever they want to do that. They'll still end up saving time from the UI actually being responsive instead of loading 50 different JS libraries just to render a textbox.
Spotify sometimes manages to somehow get into a state where typing in the search box will end up typing everything in reverse, so instead of "Don't" the box contains "t'noD". The only thing that seems to get it out of this state is losing window focus. Just losing focus on the search box doesn't help.
I had similar issues in Ontraport where if I typed too quickly my cursor would suddenly jump to the start of the textbox. I noticed I had to slow down like a hunt and peck typist and it wouldn't happen. I wonder if it was better for people who live near the server since it could be due to cross-Pacific latency.
I did try copy/pasting from another program, but formatting bugs made that unreliable.
I had this bug trying to implement a text editor using Draft.js but not sure it was for the same reason.
I guess tumblr devs tried to implement a text editor and at the same time have some vim like shortcuts(jkl).
This makes you appreciate how less can be more.