Not wanting to sound too negative, but I believe the matrix wysiwyg editor is based on a product (htmlarea) which ceased development some time ago. Even before it ceased development, however, it was looking very long in the tooth and in need of an update.
So, what is the plan?
The editor in my wordpress blog is far nicer than htmlarea - I'm sure many others are too. The 'modern' wysiwyg: presents clean raw html markup; allows for the easy selection of html elements; integrates with the browser's spellchecker (mozilla/IE7); works in safari… the list goes on. Is there any prospect of an upgrade for matrix?
This question has been asked previously.
MySource 4 will introduce a new (and better) WYSIWYG, but there is no scheduled release date yet.
As HTMLarea has been heavily modified by Squiz for use with Matrix, there are no plans on replacing the WYSIWYG Editor unless a client choses to fund this development.
As Dan says, MySource 4.0 will feature a brand-new WYSIWYG editor written completely by Squiz.
[quote]As HTMLarea has been heavily modified by Squiz for use with Matrix, there are no plans on replacing the WYSIWYG Editor unless a client choses to fund this development.
As Dan says, MySource 4.0 will feature a brand-new WYSIWYG editor written completely by Squiz.[/quote]
Yes, what Dan said 
yeah, but I added the hint that clients could possibly fund development. Always remember to upsell the larger meal. :P
What happens to clients who get gray hair as well as headaches using the WYSIWYG editors in general :P' /> <img src='http://forums.matrix.squiz.net/public/style_emoticons/<#EMO_DIR#>/laugh.gif' class='bbc_emoticon' alt=':lol: <br /> <br /> cheers :lol:
Nah, you already said that:
http://forums.matrix.squiz.net/index.php?showtopic=2268&view=findpost&p=11558
:D
Amusing banter, but this problem is still driving me nuts. Actually, I'm beginning to think one aspect could be classified as a bug. Consider this:
I have a style sheet (custom.css) which adds a background image that doesn't play nice in the simple edit wysiwyg.
One approach I tried was to use a conditional area.
[codebox]<MySource_AREA id_name="simple_edit" design_area="show_if">
<MySource_SET name="condition" value="simple_edit_mode" />
<MySource_ELSE>
<link rel="stylesheet" type="text/css" href="mysource_files/custom.css" media="screen" />
</MySource_ELSE>
</MySource_AREA>[/codebox]
…which, to my way of thinking, should have removed the offending style sheet in simple edit.
Well, it does - until you enter the wysiwyg when it rears it's ugly head again. I'm still in Simple Edit mode, but my css is back! That's not right, surely.
Its because the WYSIWYG Editor is being printed into an iframe, so the design isn't applied. My advice is to move that CSS into a CSS File asset, which is never applied to the WYSIWYG. You could also log this as a bug at http://bugs.matrix.squiz.ne.