I have always hated wysiwyg editors but most of the applications I develop they are necessary for our clients to edit their content. After trying out a few different ones I seemed to like tinyMCE the best. Although powerful and seems to generate fairly good HTML it is not without its issues. Recently I have been thinking about creating a custom wysiwyg that suits my needs perfectly taking advantage of the contentEditable attribute. Is this HTML5 feature ready? Will I have many cross browser issues? What are its limitations? I guess my question finally boils down to; Will it be worth throwing in the towel on 3rd party wysiwygs and moving to contentEditable regions?
+2
A:
The third party wysiwyg editors will also use the contenteditable attribute. The biggest problems is that they really do create tag soup and the same text created in different user agents will have different HTML source.
Personally I would say that you should stick with tinyMCE of CKEdit.
Mike Ratcliffe
2010-06-08 17:10:12
I noticed that with Cute Editor. if safari or chrome was used I had spans all over the place with "appleStyle" class. I guess I will probably face the same challenges.
Mike
2010-06-08 17:27:14
A:
Why not to try wysiwyM editor instead of wysiwyG? www.wymeditor.org Let know, if it suits Your needs.
Vladislav
2010-06-08 19:00:31