@marichrysanthemum: ikr this problem has been forever

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"

I continue to have the problem noted below that was posted in the last version of Opera One (See Below in this post). This new version has it also, (I noticed one other person replied to that post that he also has it, so it is not just me::

"For Opera One (version: 120.0.5543.38), I use Windows 10 and turn off my laptop each evening. Next morning upon booting usually Opera is the first application I open, and as often as not Opera is non responding, to the point of not being able to even close it, I have to use the Task Manager to do that, sign out of Windows and re-enter, then Opera will work. Haven't tried the newest Opera 120.0.5543.61 Stable update but will try that today."

@leocg said in Opera 120.0.5543.53 beta update:

@whisperer said :

. But I do have trouble with the changelog entry "DNA-123014 Promote 120 to stable" listed for the build 120.0.5543.53 in the full changelog. From the user's perspective that doesn't make sense.

That could be an example of things being complicated unnecessarily.

If the changelog is for the whole main version number, of course it will show information about that version starting on developer channel, being promoted to beta and to stable.

As you yourself said: "You can see what changes were made during beta stage by looking at the build numbers." That's not the case for this changelog entry.

It is, it shows the changes from when version were in developer channel up to more recent ones in stable channel.

I expect moderators to model respectful dialogue, not dismiss users' concerns with vague, accusatory remarks. You are doubling down after being respectfully asked to stick to discussions about Opera.

Furthermore, you are dismissing two specific points I raised with general remarks which are not addressing the raised issues at all. In doing so you are undermining meaningful discussions about Opera.

I consider this trolling behavior, something you have showcased before. Responding to such behavior is not productive, so I will no longer respond to posts by you.

There is an issue with the page translation feature. Sometimes it incorrectly detects the website's language and fails to translate it.
For example, the website of the Israeli mobile operator https://www.partner.co.il.
Opera identifies it as English, but the site is actually in Hebrew.
However, this issue also exists in Chrome.
But unlike Chrome, Opera doesn't allow you to manually select the source language for translation.
I kindly ask you to add this option — and preferably make it so that the languages most often translated from appear higher on the list.
(For example, in Chrome it’s inconvenient to scroll through a hundred languages just to find Hebrew.)

@frozenfan53: Same for me. Opera engineers does not seem to use it XD

Everything is up to date, but VPN Pro doesn't work, doesn't work, doesn't work... Opera has become a complete regret. I think I'll delete it and use a new browser. Responses to support emails are very slow, and the email content is inadequate.

@krzy19 Hi there, I'm encountering a similar issue as well.
I had my wallet on the android browser and when I went to it and pressed it to make the 12-word passkey (2 days ago, upon finding out the service is retiring for the first time and being prompted to make one in the first place), it errored out.
The android browser no longer shows the crypto wallet - autoupdate?
The accounts were supposed to be synced but the browser can't find the wallet.
So, what do I do now?