Hi,
I'm glad you brougt this up, it was a problem with older verisons of FCKeditor, so I put in this logic to force TinyMCE if the browser is Opera. FCKeditor, has calimed to support Opera for a long time but back when I tried it it did not work so I added this workaround.
But you brining it up again reminded me that I had not tested the issue in more recent upgrades to FCKeditor so I just tried it just now on my local machine and it works for me using the latest version of Opera. Luckily I made it a config option so you can enable FCKeditor in Opera easily, just add this to your user.config
<add key="ForceTinyMCEInOpera" value="false" />
You may want to try it yourself with Opera on your site after making this config change to verify it is working.
No matter which editor is configured, if javascript is disabled the user gets a plain text area. While the editor if enabled does make it more difficult to enter some things like javascript if the source toolbar isn't available, one cannot rely on that kind of protection but must not trust any user input other than from specific trusted users, so use of NeatHtml is essential anywhere that untrusted users may enter content.
Its not easy/possible to use rich media like javascript widgets and videos and other embedded objects using NeatHtml, so in the Blog and the Html Content module and some other features we assume a trusted user and do not use NeatHtml, but in Forums and blog comments we use it. So we are treating our content authors and blog users as trusted users.
Best,
Joe