Posts made by whisperer

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

The issue on opera://update/ still remains, where the contours of the "Check for update" is visible when disabled, but invisible when enabled.

Still not fixed:
@whisperer said in Opera 120:

About pressing Ctrl+/ in private mode:

@marinaz909 said in Opera 119.0.5497.56 Stable update:

@whisperer If I understand correctly, you see a darkened screen but no popup informing you that Aria isn’t available in private mode...

@whisperer said in Opera 119.0.5497.56 Stable update:

@marinaz909
I'm using the Windows version. It's because I open directly into private mode by right-clicking the Opera icon in the task bar. It doesn't happen when I first open Opera in normal mode and then open a private mode window. A screenshot will of course not help in this case. You got it right, I just get a darkened screen, nothing more.

Issue not fixed or back again in Opera 120.

@daria19 said in Opera 120.0.5543.53 beta update:

@francehelders: Hello! Beta is at 120.0.5543.53 and Stable is at 120.0.5543.61. Even though the version number 120 is the same, they’re on separate update tracks. The changelog line about "promoting to stable" just means that particular build was pushed to the stable channel...

So, you are saying that the changelog entry "promoting to stable" in the changelog of build 120.0.5543.53 means that build was pushed to the stable channel. But it never was, right?

@leocg said in Opera 120.0.5543.53 beta update:

@whisperer There's 120 stable and 120 beta at the moment.

You mean a beta that according to its changelog promotes itself to a stable version but still remains a beta?

@leocg said in Opera 120.0.5543.53 beta update:

@francehelders It doesn't prevent beta channel to be updated

What do you mean? Version 120 is no longer a beta, right?

And this "beta" again lists this change:

DNA-123014 Promote 120 to stable

For a complete rundown, take a look at the changelog.

Why was the changelog page removed?

When right-clicking a page and choosing Translate to English and Opera thinks the page is already in English, the translate feature is shortly displayed and quickly replaced with:

There seems to be no way to force a translation to English anyway, and no way to choose a translation to another language.

About pressing Ctrl+/ in private mode:

@marinaz909 said in Opera 119.0.5497.56 Stable update:

@whisperer If I understand correctly, you see a darkened screen but no popup informing you that Aria isn’t available in private mode...

@whisperer said in Opera 119.0.5497.56 Stable update:

@marinaz909
I'm using the Windows version. It's because I open directly into private mode by right-clicking the Opera icon in the task bar. It doesn't happen when I first open Opera in normal mode and then open a private mode window. A screenshot will of course not help in this case. You got it right, I just get a darkened screen, nothing more.

Issue not fixed or back again in Opera 120.

Not much priority is given to visual bugs, is there? It takes too long for bugs to get fixed. Doesn't Opera understand that visual bugs also hinder usability?

Like this view after having viewed a page fullscreen:

Pretty annoying.

@daria19 said in Opera 119.0.5497.88 Stable update:

@whisperer: Thanks for reporting this! The issue has already been fixed in the Developer channel and should be making its way to the Stable build soon. The fix is on the way!

To be honest, I find the quality of Opera's stable versions embarrassingly low. Someone described it as Opera being like a hobby project. I think I have to agree with that. I feel sad that I have to lower my expectations for Opera to such a level.

@andrew84 said in Opera 119.0.5497.88 Stable update:

I don't like the tab island feature in current view ...
...
Also, items in the dropdown are not highlighted when hovered.

Confirmed in light mode. They are highlighted in dark mode.

I'm working in private mode and dark mode (Windows) and press F11 (full screen) and F11 again to exit full screen. Now I hover over a link and my address bar and bookmarks bar look like this:

@daria19 said in Opera 119.0.5497.88 Stable update:

@whisperer: Thanks for the feedback! The changelog focuses mainly on major changes. We understand that smaller fixes matter too and will try to improve the detail in future updates.

A fix for a crash when accessing the menu is a minor change? Shouldn't the user be able to determine from the changelog whether this kind of bugs are fixed and thus worth it to update?