I'll be committing that change in my next update.
It will be going with Webkit in the next few versions, they already announced it, but when is another matter entirely?
Opera 14.x+ will be WebKit-based. (They're skipping version 13, just like I did for Kyôdai Mahjongg... No kidding :lol:
But it's not planned to be in beta before at least this summer, IIRC.
And the final version is probably only coming at the end of the year. Which would allow Opera to resume its earlier version numbering system (right before 2011, they released version 11. They did that every year, at least in recent years.)
Also, Presto-based versions will still be out in the wild, and supported for quite some time.
However, I don't know if it's worth bothering. Opera 12+ is so unstable these days, very few power users keep using it. I know I was a die-hard Opera fan (see the topic I posted here about their move to WebKit), and only changed to another browser reluctantly after many weeks of suffering to their various recent versions that would all keep crashing on me -- even when installed fresh.
I know how hard it can be to keep a release stable on so many different machines, but I don't think I have an exotic rig at all.
And these days, I've started using Sleipnir, perhaps because it's Japanese and is based on Norse mythology (I love both cultures..?), or just because after Opera, it's probably the best browser for multi-tab support. It has grouped tabs, and vertical tabs. It's only missing the ability to scroll a vertical list, it will only reduce individual tab heights, but it's still better than using Opera and having to restart it every hour or so.... :-/
Yep, Sleipnir is a pretty good Chromium fork.
It won't be that long, but given how Opera's market share is even smaller than IE6's - and we largely already dropped IE 6 support, it does seem something of a lost cause.
Let's just say, I've wasted way too much time on IE6, not because of its market share, but because I had a strong belief that if I was supporting Opera first thing, then I should be supporting to any browser that has a higher market share. Well, in the case of IE6, if you remove China from the picture, its market share is now less than Opera, so there's your first good reason for dropping support for IE6, but also -- I've made so many changes to Wess over the years, and every time I had to patch it for IE & co... One day, not so long ago, I realized I'd better support the most widely used browser (i.e. a WebKit-based one), and then, *when we go public*, fix bugs as they're reported on other browsers.
I'm not effectively doing that, but let's just say I'm in a better shape now that I stopped worrying and learned to love the chrome ;)
You do realise that IS the "won't fix" solution, right?
I would venture into saying it isn't.
wontfix means no changes will be made.
notabug is similar, but might imply a change. So this situation would be more of a notabug.
Anyway, since it's a browser bug and it happens so randomly, I'll be removing support for Opera in can_flex. You can always add it yourself in your CSS (i.e. "@if (can_flex, opera[12.1-])"...)
Another thing I'd like to point out, is that even Firefox and Chrome weren't cooperating with me when it came to adding flex support. The basic version failed to work when I would add a code block inside a post. I managed to patch them, but only because I found hints online about making them behave. NOT because I'd done something incorrectly in the first place, which is a bit worrying...
so, flexbox is a feature I love, but if it's not 'stable' by next year, might be worth considering to drop it entirely...