I'm getting used to this. I've even learnt to expect it and prepare myself mentally. It's still true: releasing something is the most depressing job for somebody doing quality assurance.
So we finally have a new flagship desktop version. The long-awaited Opera 9.5 launched with – I hope – all the hype and thunder we could drum up. Literally thousands of bug fixes since the 9.2x versions, a fancy new skin, new features like getters and setters and Dragonfly that will make much of my work much easier – and yet I can think of few other things than the REMAINING bugs that we should have fixed. It's QA release blues time. Happened every time since Opera 6 final or so.
And with a new release comes new problems. The worst current compatibility issue is a problem with the TinyMCE editor, where legacy versions of TinyMCE will re-arrange your sentences in somewhat unpredictable ways when you press enter. (This is caused by TinyMCE detecting Opera to work around a bug in earlier Opera versions – we've now fixed the bug and unfortunately their workaround still runs and messes things up). To put this problem into the right perspective, TinyMCE is the default editor for WordPress, and all admin screens in the millions of WordPress installations out there are now suddenly broken in Opera. Ouch, Sir. What a gotcha!
This is fortunately precisely the sort of things we have browser.js for. There is a fix in already, needs some more tweaking to run in WordPress' admin screen but I'll get that done. So thank God and Lars Erik for browser.js – when I can throw some fixes in after the final launch, release blues isn't quite as bad as it used to be :).
I'm crossing my fingers that the patch will eventually be robust enough to work with most legacy TinyMCE installations out there. Wish me luck – or even better, tell me where it fails ;-o