On the title page of module wrote:
compatible with most of the internet browsers, including
Opera 9.5+ (FCKeditor 2.5+)
Safari 3.0+ (FCKeditor 2.5+)

BUT!
On the dev page (http://dev.fckeditor.net/roadmap) of FCK editor we could see:
Milestone: Opera Compatibility - 81% - Closed tickets: 88 Active tickets: 20 / Total tickets: 108
We are in straight collaboration with Opera Software to make their browser compatible with FCKeditor.

Milestone: Safari Compatibility - 77% - Closed tickets: 59 Active tickets: 18 / Total tickets: 77
This milestone will be used to group tickets relative to the compatibility of FCKeditor with Safari. Once we'll announce the compatibility, the milestone will not anymore exist, and all Safari bugs will be moved to the normal tickets system.
We are working together with the developers of Safari's core software, named WebKit, to fix both sides. It means that not only FCKeditor must be fixed, but also Safari needs fixes to be able to work properly.

Safari and Opera compatibility is limited. With Opera and Safari FCK does NOT working properly yet.

Comments

wwalc’s picture

wwalc commented
Assigned: Logrise » Unassigned
Status: Needs work » Closed (works as designed)

FCKeditor is stable enough in all mentioned browsers (even in Opera and Safari), that's why they're listed there.

To be honest, every wysiwyg editor has to deal with various bugs in internet browsers and none is fully compatible with each browser. What's more annoying, FCKeditor must be updated regularly to maintain compatibility with newer versions of these browsers because almost each new version of a browser introduces a feature that breaks something.
That's why there are also tickets targeted only to IE or FF.