Opera 119.0.5497.88 Stable update
-
andrew84 last edited by andrew84
@SheriffOfGrace there's mistake in the both blog post and changelog.
135.0.7049.42 is actual for Developer version. -
SheriffOfGrace last edited by@andrew84 It may be so, it may be not: As even beta is already on 135.0.7049.115 for eight days already.
-
pilis00 last edited byThis issue still persists.
https://forums.opera.com/topic/84820/duplicated-audio-desynchronizes-if-i-switch-to-other-tabsCan't you import the fix into Opera? It was fixed in Chromium 136.
-
-
SheriffOfGrace last edited by
@andrew84 I see, that's what they also say on their blogs. But in Beta's case, they give us this:
That's already from more than a week ago. So I wouldn't count it as unrealistic to moving 119 to the same Chromium as you have on Developer. -
-
SheriffOfGrace last edited by
It doesn't matter anyway, as we're dealing with lots of open vulnerabilities, as it seems.
It has also detected version 134 BTW.
-
andrew84 last edited by
@SheriffOfGrace said in Opera 119.0.5497.88 Stable update:
detected version 134 BT
Sure the version on 'About' page is correct one. It just some typo in the blog and most probably will be fixed soon.
-
antonio1678 last edited by
Ha, about page says 134. So you are totally behind on Chromium updates for security and lie in the changelog. Are we a joke to you?
-
antonio1678 last edited by
@andrew84: That is a third party site, so it is what Opera is reporting about itself from the browser. Also the about page says 134. Did you even check yourself?
-
andrew84 last edited by
@antonio1678 said in Opera 119.0.5497.88 Stable update:
Did you even check yourself?
what exactly I should check more?
-
SheriffOfGrace last edited by
@andrew84 He misunderstood you, actually. He thinks you were claiming they were on 135, whereas you stated the contrary.
-
-
whisperer last edited by"Here is the full changelog."
Hardly. Why is so little listed there? I mean the crash when hovering over the Bookmarks menus is fixed too. Wasn't that worth mentioning?
-
deathcat last edited byThey can't update the engine, they're lagging behind the original as amateurs, and not a serious company by 3 numbers, so they just started lying that it was updated. Well done.
-
deathcat last edited by
@antonio1678: Now copy-paste will give out that they carefully test and care about your well-being, and 134 is 135 or it is a cosmetic bug))) They have bred a lot of garbage with GX and Air, and the corpse of Neon has surfaced with some AI functions, and there are not enough people to do all this nonsense. As a result, the main line of the browser is as if it is being done by a couple of people as a hobby.
-
SheriffOfGrace last edited by
To be honest: They haven't corrected neither blog post nor changelog so far.
In another thread I asked about Opera trailing three versions of Chromium and I got this answer:
https://forums.opera.com/topic/84462/general-reliability-security-and-privacy-of-opera/12
Make of it, what you want! -
deathcat last edited by
@andrew84: It's a mess because the company doesn't have a strategy, they don't know who they're making the browser for and why. They have underdeveloped games in the form of Crypto, GX, Air, Neon, and apparently there is no limit to this idiocy, as a result, bugs on a normal browser are not fixed, and they even have a leaky 135 on their Dev channel, when 138 is already stable for other developers.
-
SheriffOfGrace last edited by
@deathcat I don’t think, anybody forces you to use this browser or their siblings. You can use them for free. If you do despise them so much, just hop off and use another. There are plenty. If you are so pissed off you might want to do this.
I‘m also playing with this thought like maybe a few others too. I‘m wondering and asking, still. And I‘m aware that no other browser comes without issues. -
andrew84 last edited by
@SheriffOfGrace That's was some standart answer about features. Edge also have a bunch of features and it's on 137 version. You may say that the development team is much more bigger there. Yes, of course. But at the same time, if the development resource is limited, there's no need to release and support different browsers. And regarding the features, some features (old ones) still don't work as expected. That's why I'm stuck on pre-One version. So for me the feature support is not an argument to excuse the versions delay.
