Posts made by deathcat

What's this crap that's appeared, and why can't I remove it? I click "Don't show again," but it reappears after opening a new tab or restarting the browser. They can't update the engine, but they still manage to shove in more junk.

@leocg: I already realized you're talking nonsense, or, like Opera, pretending not to understand what you're talking about. Chromium 144 should already be testing on the developer channel, so they can then move to the stable channel, as they did before, lagging behind by a couple of weeks. Now they're stuck on 140 and can't seem to make any progress.

@leocg: Opera's stable channel currently has Chromium: 140.0.7339.249. Where did you find 142? In a couple of days, 143 will be stable. Other developers are already testing 144 on their Dev channels. So, the question arises: why is Chromium still relevant in Opera, even on the Dev channel, where they're stuck on 140.0.7339.208?

@leocg: By the time they update to 141 or 142, their competitors will already be on 145 or 146. That's why one wonders what kind of mess is going on with Opera's developers, that they're unable to support the current engine and are lagging behind like some amateur startup. I'm not even talking about the slew of minor bugs that haven't been fixed for years. They've released a bunch of different browser versions and can't make any of them current and stable.

Are you not planning on updating your Chromium version, or have you forgotten how? The Dev version is running on the rotten 140 engine.

The interface twitches when I type an address in the command line. It's annoying.

The interface twitches when I type an address in the command line. It's annoying.

This is already the level of amateur developers who are not able to keep the browser up to date. Soon the release of 139 Chrome, and the version of Chromium on the developer channel is older than on the stable channel and has not been updated for more than a month and a half. If this is how you create the appearance of supporting Manifest 2, then this is a pitiful sight. Why then is there still a warning that your browser will also soon stop supporting the extensions of the second manifest? It would be possible to understand that you are seriously fixing something in the engine, but it seems that you are trying to delay the end of support, and are not doing serious work with the engine so that it supports Manifest 2, you do not have the resources for this. So far, disrespect for users is visible. They do not even backport critical holes, i.e. browser security is no longer a priority. I am waiting for the next scripted phrase of the bot: "We are thoroughly testing to improve the user experience"

Flow stopped working. Resetting and rebooting do not help. Through opera.com/connect it also constantly hangs and there is no barcode.

@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.

@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.

They 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.

Where did the currency conversion Russian rubles go? There is no RUB in the settings list.On R only Romanian leu.

@daria19: The same meaningless answer.

What's going on that the chromium version isn't updated at all?

@daria19 On the developer channel, the version of chromium has not been updated for the second month and is stuck on beta version 133, although there is already a final 135. I repeat, instead of breeding dozens of browsers, they should have done one normal one. And you already answered this, about how thoroughly the functions are tested, only there are more and more bugs and it is not clear whether you are on the stable channel or on the beta/dev.

@andrew84 I reinstalled the latest developer version and the option is there, but it definitely wasn't there the first time. Well, if it's a bug, then it's forgiven for now, but it's even better to completely disable ARIA via flags.

@leocg: Are you deliberately not reading my message? My screenshot is from the development version, and I provided the build number. There is no setting to remove this junk from the interface.

@leocg There are no new settings, just the ones that were there.

They just messed up the interface and didn't bother to add settings to disable it.