Comments on: Tales of the Rich Text Editor and Safari Support http://ajaxian.com/archives/tales-of-the-rich-text-editor-and-safari-support Cleaning up the web with Ajax Thu, 09 Feb 2012 06:55:33 +0000 hourly 1 http://wordpress.org/?v=3.2 By: zero0x http://ajaxian.com/archives/tales-of-the-rich-text-editor-and-safari-support/comment-page-1#comment-260402 zero0x Sat, 05 Jan 2008 14:25:49 +0000 http://ajaxian.com/archives/tales-of-the-rich-text-editor-and-safari-support#comment-260402 And the solution is: Don't use text editor! In a great CMS there is no Rich Editor needed. Want long documents? That's not what web is for! Give 'em PDF! Want short info about products, employees, etc.? Create template and save data in JSON! The customers will enter: Name of the product, Price, etc. And template will do ALL formatting! I don't know if there is a CMS like this, but I AM GOING TO DEVELOP it and sell it and buy a Macbook :P:P:P Have a great day Ajax-guys! And the solution is:

Don’t use text editor!

In a great CMS there is no Rich Editor needed.

Want long documents? That’s not what web is for! Give ‘em PDF!

Want short info about products, employees, etc.? Create template and save data in JSON! The customers will enter: Name of the product, Price, etc. And template will do ALL formatting!

I don’t know if there is a CMS like this, but I AM GOING TO DEVELOP it and sell it and buy a Macbook :P:P:P

Have a great day Ajax-guys!

]]> By: Paul Howson http://ajaxian.com/archives/tales-of-the-rich-text-editor-and-safari-support/comment-page-1#comment-254742 Paul Howson Thu, 30 Aug 2007 19:55:11 +0000 http://ajaxian.com/archives/tales-of-the-rich-text-editor-and-safari-support#comment-254742 The problem with rich text editors is that they allow users to add arbitrary formatting to content rather than adhering to the css styles which a site designer has set up. So there's a need for another kind of embedded editor also -- one that only allows formatting by defined CSS styles. That means no font menu, or font size menu in particular. Since many people get bamboozled by lots of buttons, the editor needs to be visually very simple -- just the minimum of controls to select allowable CSS styles. The problem with rich text editors is that they allow users to add arbitrary formatting to content rather than adhering to the css styles which a site designer has set up.

So there’s a need for another kind of embedded editor also — one that only allows formatting by defined CSS styles. That means no font menu, or font size menu in particular. Since many people get bamboozled by lots of buttons, the editor needs to be visually very simple — just the minimum of controls to select allowable CSS styles.

]]> By: Spocke http://ajaxian.com/archives/tales-of-the-rich-text-editor-and-safari-support/comment-page-1#comment-253979 Spocke Thu, 16 Aug 2007 17:41:54 +0000 http://ajaxian.com/archives/tales-of-the-rich-text-editor-and-safari-support#comment-253979 The main problem on Safari 2.x is the lack of a proper selection object there is no way to get a DOM Range of the currently selected contents in Safari 2.x. But in 3.x they have implemented this possibility, this was a major show stopper to get TinyMCE to work properly on Safari and it's kind of hard to fake if there isn't an API available for it. Another missing thing is that Safari doesn't provide image selection support there is no visual representation when you select them. This shortcoming is reported to the Safari guys so I hope they fix it soon and that they focus more on the RTE support. Safari might be ahead on the CSS implementation but they are still behind when it comes to JS APIs. The main problem on Safari 2.x is the lack of a proper selection object there is no way to get a DOM Range of the currently selected contents in Safari 2.x. But in 3.x they have implemented this possibility, this was a major show stopper to get TinyMCE to work properly on Safari and it’s kind of hard to fake if there isn’t an API available for it.

Another missing thing is that Safari doesn’t provide image selection support there is no visual representation when you select them. This shortcoming is reported to the Safari guys so I hope they fix it soon and that they focus more on the RTE support.

Safari might be ahead on the CSS implementation but they are still behind when it comes to JS APIs.

]]> By: Mike http://ajaxian.com/archives/tales-of-the-rich-text-editor-and-safari-support/comment-page-1#comment-253976 Mike Thu, 16 Aug 2007 17:24:16 +0000 http://ajaxian.com/archives/tales-of-the-rich-text-editor-and-safari-support#comment-253976 You think we will ever be able to just say this? <code> <textarea rich="true"></textarea> </code> You think we will ever be able to just say this?


<textarea rich="true"></textarea>

]]> By: Soren Vejrum http://ajaxian.com/archives/tales-of-the-rich-text-editor-and-safari-support/comment-page-1#comment-253975 Soren Vejrum Thu, 16 Aug 2007 16:52:55 +0000 http://ajaxian.com/archives/tales-of-the-rich-text-editor-and-safari-support#comment-253975 The rich text editor support in Safari is quite limited and has many errors, which need to be worked around for more than very basic rich text editing and formatting. We have actually fully supported Safari in our Asbru Web Content Editor (editor.abrusoft.com) since September 2005! It has been and still is a lot of hard work and many other developers have given up - but it is doable. The rich text editor support in Safari is quite limited and has many errors, which need to be worked around for more than very basic rich text editing and formatting.

We have actually fully supported Safari in our Asbru Web Content Editor (editor.abrusoft.com) since September 2005! It has been and still is a lot of hard work and many other developers have given up – but it is doable.

]]> By: anonymous http://ajaxian.com/archives/tales-of-the-rich-text-editor-and-safari-support/comment-page-1#comment-253966 anonymous Thu, 16 Aug 2007 15:21:22 +0000 http://ajaxian.com/archives/tales-of-the-rich-text-editor-and-safari-support#comment-253966 yep,i've also spent good hours with that damn safari,and ended up with my own simple safari-only editor (for others i used FCK), based on some free text editor (don't remember thename). The biggest challenge is tabbed layouts. Safari has some kind "optimization". If IFRAME not visible, it unloads it's content. So imagine, you have 2 tabs, one of them with editor. User first edit some html, then switch to another tab and then back. What the... editor is gone?! Yep... it is. You need to re-initialize editor each time you want to show it. Also you need to wait some time before editor document will be available afrer IFRAME refreshes on showing. I don't remember all hacks i needed to apply to my code, but Safari is really pain in the ass. I hope 3.0 will be much more coding friendly yep,i’ve also spent good hours with that damn safari,and ended up with my own simple safari-only editor (for others i used FCK), based on some free text editor (don’t remember thename).
The biggest challenge is tabbed layouts. Safari has some kind “optimization”. If IFRAME not visible, it unloads it’s content. So imagine, you have 2 tabs, one of them with editor. User first edit some html, then switch to another tab and then back. What the… editor is gone?! Yep… it is. You need to re-initialize editor each time you want to show it. Also you need to wait some time before editor document will be available afrer IFRAME refreshes on showing.
I don’t remember all hacks i needed to apply to my code, but Safari is really pain in the ass. I hope 3.0 will be much more coding friendly

]]>