4 ms·
It breaks Pentadactyl external editor feature as every other WYSIWYG editor do. This will be a pain to use.
by l-p 11y ago
It breaks Pentadactyl external editor feature as every other WYSIWYG
editor do.
This will be a pain to use.
- tomsthumb 11y agoiirc you can disable pentadactyl on a per page/per domain basis, unless that was some other vim browser plugin. it's been a while.
- louhike 11y agoPentadactyl is a browser extension used by very few people, why should they try to make it work with it?
- MarkCole 11y agoIf EVERY WYSIWYG editor is breaking the plugin. Maybe it's the plugin that is broken not the editors? Just a thought.
- l-p 11y agoActually, not every editor break it, this is not my real issue with WYSIWYG editors anyway. My problem is that I don't want to use them. Unless they use markdown or another simple formatting language behind the scene, and allow you to switch to a simple `<textarea>` input, you can't avoid them. I already have a text editor, I already have a way to generate "rich" text, I don't need another tool with another set of bindings, quirks, bugs and incompatibilities. Every editor has its own way to deal with very basic stuff: when writing a list what happens if you press return twice? Backspace on an empty element? Tab? You can't know beforehand. I'm fine with giving tools to non-technical users, but there should be a way to disable such editors completely so it can adapt to any workflow.