I've just identified two problematic and related behaviors in Safari 3 (Tiger):
If you compose a message and preview it, when you submit, all formatting will be broken: Paragraph ends and beginnings will be transformed into the plain text word "div", and bold/italic formatting will be broken and leave behind nothing but part of a span tag. This appears to be related to the fact that the editor behaves radically differently at the code level in Safari than it does in Firefox.
Second thing is that if you use nicEdit in Safari (3), you get a lot of extraneous code. As I've said, this seems to be related to the first point.
As a workaround, could you create a config option to disable the editor in Safari? This behavior is ugly enough that you really don't want Safari users touching it.
Comments
Comment #1
mcrittenden commentedWon't fix now that Wysiwyg is being used instead.