This topic was marked solved by its starter, on March 28th, 2013, 09:09 PM

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: flexbox and opera 12.14
« Reply #15, on March 26th, 2013, 02:08 AM »
Quote from MultiformeIngegno on March 26th, 2013, 01:47 AM
Shouldn't Opera go with WebKit soon? Its share is already ridiculous, when the browser engine will change this wont be a problem anymore.
I think this should be a not-a-bug / won't fix
It will be going with Webkit in the next few versions, they already announced it, but when is another matter entirely?
Quote from icari on March 26th, 2013, 02:03 AM
i dont think won't fix is the way to go, as it may be a long time before opera changes the engine in the stable version of the browser. those that do use opera should not be forced to use another browser when Nao has already stated it is possible to exclude opera from flexbox and the issue is resolved.
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.
Quote
Nao has already stated it is possible to exclude opera from flexbox and the issue is resolved.
You do realise that IS the "won't fix" solution, right?
When we unite against a common enemy that attacks our ethos, it nurtures group solidarity. Trolls are sensational, yes, but we keep everyone honest. | Game Memorial

icari

  • Posts: 88
Re: flexbox and opera 12.14
« Reply #16, on March 26th, 2013, 10:33 AM »
but that is still fixing the issue for those that use opera. making the issue not exist is making it fixed imo.

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: flexbox and opera 12.14
« Reply #17, on March 26th, 2013, 03:52 PM »
You do realise that we move at our pace and not the pace of others, right? It will get fixed in due course.

Nao

  • Dadman with a boy
  • Posts: 16,063
Re: flexbox and opera 12.14
« Reply #18, on March 26th, 2013, 03:54 PM »
I'll be committing that change in my next update.
Quote from Arantor on March 26th, 2013, 02:08 AM
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.
Quote
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  ;)
Quote
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...
Re: flexbox and opera 12.14
« Reply #19, on March 26th, 2013, 06:10 PM »
Pete, I just noticed reply #17 from yours... Posted 2 minutes before mine.
I can certify I never got a mention about it being posted in the meantime.

This really, really should be looked into, because it's been a problem for a long time, and I hate the idea of missing a post...!

If it helps, my post was sent from the regular post box (it's easy to tell with me -- if it's a long post with quotes, it's the post page, otherwise it's likely to be a quick reply, like here.)

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: flexbox and opera 12.14
« Reply #20, on March 26th, 2013, 07:08 PM »
Quote
This really, really should be looked into, because it's been a problem for a long time, and I hate the idea of missing a post...!
I will investigate, but I wasn't able to reproduce it when making changes to it recently.

Nao

  • Dadman with a boy
  • Posts: 16,063
Re: flexbox and opera 12.14
« Reply #21, on March 26th, 2013, 07:21 PM »
Done.
One of the things I noticed, is that the Reply button has a last_msg param, instead of 'last'. Thus, it won't go through the code path for last post checks... (I think.)
Now, in Post2.php, it checks for $_POST['last']. I double-checked, and guess what..? Post pages don't have that one. They have (drum roll)... last_msg!

So, I'm thinking at some point I renamed last_msg to last, and forgot to rename all of them.
It's in rev 1112, by the way.
What should I do...? Rename the rest?

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: flexbox and opera 12.14
« Reply #22, on March 26th, 2013, 07:25 PM »
That makes a lot of sense. If you're going to rename them, be consistent. I have no aversion to it being either last_msg or last, so whichever you want to do. Personally I'd put them all back to last_msg as that's more descriptive than last (last what, exactly?) but I'm not bothered if you want to make them all 'last'.

Nao

  • Dadman with a boy
  • Posts: 16,063
Re: flexbox and opera 12.14
« Reply #23, on March 26th, 2013, 07:33 PM »
I renamed last_msg to last everywhere (sorry, that was before I saw your post). Checked against [^_]last_msg to make sure I caught everything. There was a surprising amount of crap that was left over. Heck, there was even a reference to that form entry in post.js...! Meaning Preview wouldn't tell us about new posts, either.

I'll commit once I'm done with my current work. I've got tons of things to commit, actually... And in all areas! (Fixes in Skeleton code, fixes in Notifications, template changes for Notifications, now this...)

PS: I prefer last to last_msg personally, perhaps because I have an aversion for underscores in 'visible' HTML code, as you may have noticed today, ah ah... Also, err, I think 'last', as a variable, is ONLY used in this situation. So there shouldn't be any conflicts...

icari

  • Posts: 88
Re: flexbox and opera 12.14
« Reply #24, on March 28th, 2013, 09:09 PM »
so far i dont see the issue occurring, so i will mark this solved. thanks.