On Thu, 30 Jun 2005, Scott Reynen wrote:
I can't speak to all of them, but for a few of your problems, the
spec was developed independently by Microsoft for use in IE, and is
not a standard. You can't expect other browser vendors to support
every random thing MS decides to stick in their browsers. That's why
we have web standards. If you're aiming for a cross-browser
application, I would recommend sticking to those standards.
Midas is a de facto standard supported not only by Microsoft,
but also by the Mozilla Foundation for Gecko-based browsers:
http://www.mozilla.org/editor/midas-spec.html
Note that the problems in the original message are not unique
to the TinyMCE WYSIWYG editor. They also occur when using
HTMLarea (http://www.dynarch.com/projects/htmlarea/) and Kupu
(http://kupu.oscom.org/), which is additional evidence that
the problems lie with Safari's incomplete support of Midas.
But, to move this to a more practical level: currently
Safari lacks good WYSIWYG editing support. This impairs
the usability of Safari with blogs, wikis, request tracking
systems, and middleware applications that support WYSIWYG
editing. Users will neither know or care about standards;
what they will know is that their favorite web-based services
currently work with both MSIE and Firefox, but not with Safari.
Please, Apple, fix this!
Finally, I'd like to thank the TinyMCE development team
at moxiecode.com for doing their best to make the most
of the limited Midas support currently in Safari. They
have taken TinyMCE much further than either HTMLarea or
Kupu in this regard. I really appreciate their efforts.
Mark Montague
The University of Michigan
email@hidden
