TorS

Opera says (in a mail to me earlier this month):

this appears to be a possible bug in Opera, depending on the JavaScript specification. We will look into whether this should be fixed by us or in the tinyMCE code.

It’s in good hands then, I guess.

Oh great! Thank you. I am more familiar with the code view anyway so I won’t miss the bugger.

Update:

-Upgraded Opera 9.20 to 9.21 today. It made no difference.
-If you by disabling wysiwyg mean run Opera without css, well that makes no difference either.
-Actually you don’t have to upload anything at all to see this bug. Write a post that includes a href tag. Look at in in “code”. Rewrite HREF as href. Switch view to “visual” and back again to “code”. It’s all caps HREF again. I am planning to disable the validation link on my blog because it’s embarrassing.
-I have filed a bug report with Opera – if for nothing else than to eliminate it from the list of suspects.

we have that issue opened in trac

Yes, good. I wasn’t aware of the significance of that fact. Please note also the second issue: Paragraphs which should have been floated left or right are broken and the end part rendered below.

Checked things with Firefox. Both issues non-existant. I do need a fix that would allow me (and the rest my family, not least) to post legit XHTML in WordPress, using Opera.

(Sorry, I did not notice your posts before I posted my own follow up.)

I use Opera 9.20. When you say disable wysiwyg, do you mean in Opera or WordPress?

I have now upgraded to WP 2.2 and the problem persists. There is another one, too. In connection with class=alignrigt (or -left) paragraphs are broken. Only a part of it remains on the side of the image while the rest is rendered below.