3 ms·
It's great that it's small, but it suffers from the same horrible interactions that most other web editors also suffer from. Try quoting the last paragraph in
by notzorbo3 9y ago
It's great that it's small, but it suffers from the same horrible interactions that most other web editors also suffer from.
Try quoting the last paragraph in the editor. It's now impossible to ever escape from the quote. All new text at the bottom stays "quoted".
From a cursory test of the editor, it suffers from basically all the issues that contenteditable suffers from.
The reason other editors are so big is because the take editing behaviour into account.
- Veedrac 9y agoWorks for me in Chrome 60. Just return twice, like a normal editor.
- c-smile 9y agoTry to insert text between two tables: <table>...</table><table>...</table> ... That's the same problem. At the moment caret positions in browsers are limited only by char-positions. There are no carets in between box blocks. Yet consider my question on SO : https://ux.stackexchange.com/questions/72309/caret-positioning-in-html-richtext-wysiwyg-editor https://ux.stackexchange.com/questions/72309/caret-positioni...
- jancsika 9y ago> The reason other editors are so big is because the take editing behaviour into account. It doesn't take it into account as much as it hoists an implicit imperative programming language onto it. Of course learning markdown for a non-technical user isn't easy, and having a separate "Preview" pane to show the final product certainly isn't a great UX. But it is a delight compared to "for a simple URL, I type the URL, click <Enter>, then either click the 'X' on the big preview graphic that inescapably appears or click <ctrl-z> then enter again to get rid of whatever <div> monstrosity Yahoo just added to my message."