When you set an HTML element, let’s say a, as contenteditable, you expect that several common actions work right away, but the sad truth is that you instead need to fix a lot of these behaviours, to be able to produce a good semantic out of the inserted text when paste, formatting and new lines are created in the contenteditable itself. But we want to use, and I will not annoy you regarding the reasons of using it in place of because you can easily perform a Google search about this topic. The editor is smart enough to remove the second element, append the text node into the first one and “ normalize” it to a single element with a single text node inside. By default, the browsers start to add and acting in ways that are creating a real mess and confusion inside the HTML code, so there is a lot of work to be done “ behind the curtains” to correct all these default behaviours. And, after the first days of meeting contenteditable=”true”, I started to realize that things were not so straight forward as they looked.
Imperavi redactor download code#
When I wanted to dig more into this topic, I started to take a look to the HTML code of the Medium editor, and I did the same thing with the Redactor’s one. So, let’s make this very clear, you DON’T have to create your personal WYSIWYG editor, most of all if you don’t have the possibility to dedicate months to it: contenteditable is not a standard and it creates several different problems in different browsers, so it’s a path that you don’t want to take, unless you know what you’re doing but, also in that case, think about it twice please! ) Discovering contenteditable Redactor, on the other way, besides its price, it proved to be useful for our projects, easy to customize and integrate with custom code, and it fits pretty well in our designs, but it creates really a lot of automatic and useless (at least for me) HTML elements that, in my opinion, tends to make the work of the content editors harder because it’s very easy to paste text in the wrong elements, without you even noticing it if you don’t check the HTML code/view available inside the Redactor editor. CKEditor proved to be hard to include in our minification process (powered by Grunt) and, not to be forgotten, in fleka we always try to aim for the best possible UX: using CKEditor it’s not easy at all for us to customize it to perfectly fit inside our custom design.
We tried several WYSIWYG editors, among all CKEditor and Redactor, but when these tools go in the hands of the final users (aka our Clients), the problems start popping out they - of course - are not able to manage the HTML content, and they - of course - copy and paste text from any kind of source (ie:Word) carrying with it a lot of strange tags and HTML elements.ĭon’t take me wrong, CKEditor is a very powerful, open sourced, community driven project and you can really do a LOT of things with it I was simply trying to find a more ‘ elegant’ and easy solution for our AngularJS projects, building an AngularJS component that could have been easy implemented in all our web apps. Once you have read the articles above, you could then ask !WHY! Tell me only WHY!? Well, the because is that the alternatives are not working well for the projects we develop for our Client fleka.
Imperavi redactor download software#
First of all, to understand my pain, read this article “ Why contenteditable is terrible” by Nick Santos, Software Engineer if that wouldn’t be enough, you can have a clearer vision about contenteditable reading “ ContentEditable - The Good, the Bad and the Ugly” by Piotrek Koszuliński, CKEditor lead developer.
0 kommentar(er)
