- I click on the + to open a new tab.
- In the Speed Dial page, I right-click a link and choose Edit.
- The address field is empty and it seems I am no longer able to edit a bookmark this way.
(Opera for Windows 125.0.5729.49)
Do more on the web, with a fast and secure browser!
Download Opera browser with:
(Opera for Windows 125.0.5729.49)
@whisperer said in Opera 125 Stable:
Using the Windows version of Opera in dark mode, go to password manager (opera://password-manager/passwords) and click the Add button. There is no visible cursor..
There is no cursor in dark mode when editing any options in preferences.
I work with Opera for Windows and have the sidebar disabled. I use a user defined hotkey to enable/disable the sidebar whenever I want. When marking a test on a webpage, several option appear (Search , Copy, Snapshot) and the option to use Opera AI to translate and other options. When selecting to use Opera AI in the popup options, the sidebar gets enabled, which should not happen.
Using the Windows version of Opera in dark mode, go to password manager (opera://password-manager/passwords) and click the Add button. There is no visible cursor..
@whisperer said in Opera 123:
Ctrl+Enter still not working (Windows version).
Is it just me?
@whisperer said in Opera 122.0.5643.71 Stable update:Ctrl+Enter no longer works (Opera 122.0.5643.71 on Windows).
If I type opera in the address bar and press Ctrl+Enter, the text changes to www.opera.com but the previously displayed website is shown instead of www.opera.com.
Still not working in version 124.
@Opera-QA-Team said in Opera 123:
@whisperer: Ok, I see the point now. It is changed from the build 124 becasue of the new AI chat panel, so the screen won't be grayed out anymore.
It's not fixed in build 124.
@Opera-QA-Team I open directly in private mode by right-clicking the Opera icon in the task bar. Has been reported before, see here:
https://forums.opera.com/topic/85536/opera-120-0-5543-61-stable-update/2?_=1761832194124
When using Tab and Shift+Tab navigation for the folders at the left on page opera://bookmarks/, the block cursor is still hidden for the folder that is opened.
Pressing Ctrl+/ when in private mode (Windows version) still makes the screen go dark. Instead of an error or nothing happening.
Ctrl+Enter still not working (Windows version).
Is it just me?
@whisperer said in Opera 122.0.5643.71 Stable update:
Ctrl+Enter no longer works (Opera 122.0.5643.71 on Windows).
If I type opera in the address bar and press Ctrl+Enter, the text changes to www.opera.com but the previously displayed website is shown instead of www.opera.com.
Ctrl+Enter no longer works (Opera 122.0.5643.71 on Windows).
If I type opera in the address bar and press Ctrl+Enter, the text changes to www.opera.com but the previously displayed website is shown instead of www.opera.com.
Why are people forced to tell Opera why they install Opera? Is this information sent to Opera Software and what is done with it? What exactly is stored with this information?



And here's what you get when clicking the icon:

Apparently, the popup box cannot handle long user names like "Opera Comments Bot".
@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.
@burnout426 said in Opera 120.0.5543.53 beta update:
Hovering over the "blog post" link for each and looking at the URL will show whether it's a developer, beta or stable build. You can even see if it's the initial developer/beta/stable build for that major version by the lack of "-update" in the URL. Think it would be nice if that info was in the header for each build though in the changelog.
That would indeed improve clarity. Additionally, a link to a page with an explanation of full changelog pages could be helpful too.
@leocg said in Opera 120.0.5543.53 beta update:
@whisperer Everything that is being discussed here about Beta channel have been updated to the same version of stable channel.
It's not something new, Opera has been doing it since a while already and, like I said, started by request of (some) users.
Also, Opera once said that people should follow channels and not version numbers, that only exist to make things easier for people.
That's not an answer to my question. If you are not willing to explain why you think I am unnecessarily trying to complicate things, I respectfully ask you to refrain from posting off-topic thoughts about me and stick to discussions about Opera.
I have no trouble with the existence of beta and stable builds with the same major version number. 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.
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. The explanation given that the full changelog consists of a combination of indistinguishable beta and a stable changelogs where the beta changelog can contain entries that doesn't apply to the build it is listed under, but to an earlier build, doesn't make it logical and understandable for users.
@leocg said in Opera 120.0.5543.53 beta update:
@whisperer And I think you are trying to complicate things unnecessarily.
Enlighten me, what am I trying to complicate unnecessarily and how am I trying to do that?
@leocg said in Opera 120.0.5543.53 beta update:
@whisperer The changelog is for the whole version.
You can see what changes were made during beta stage by looking at the build numbers.
Exactly my point.
@daria19 said in Opera 120.0.5543.53 beta update:
To add some context: the previous changelog entry for version 120 was about its initial stable release, and the next one referencing 120 was for the beta channel. That beta changelog includes the note that 120 is now available not only in beta but also in stable, which signals the promotion.
There is a beta changelog? Cool. Where is it? I have only seen the full changelog which contains changes of beta and stable versions without distinction.
If you need to repeat a change for an earlier stable version, why not for all the changes of the earlier stable version?
The issue on opera://bookmarks/ still remains, where there is no cursor on the folder that is open when navigating folders at the left using the keyboard (Tab key).