Opera 121.0.5593.0 developer update

[andrew84]

andrew84 last edited by

I don't see the redesigned PiP flag anymore (in Stable version still there).

But I see the 'PIP controls update 2024' flag which has no effect. Does the flag's point is to restore older PIP's controls or what? The redesigned PiP is really bad.

[andrew84]

andrew84 last edited by

And the 'Scroll to the top of the page by clicking the active tab' feature still stays broken partially. It scrolls when moving tab but it shouldn't. The bug stays more than a year despite of the multiple reports.

[andrew84]

andrew84 last edited by andrew84

DNA-123029 [Color themes] When an animated color theme is selected, a start page wallpaper can be chosen in Easy Setup

It means that it's possible to use user defined wallpaper within the themes? Or there was such possibility and that's was considered as a bug?

[andrew84]

andrew84 @vladbabinets last edited by

@vladbabinets Yes, here Edge stable is already on 138.
On the other hand, most probably V2 manifest extension will soon stop working there. So probably it will attract some portion of users to opera (especially if they really have a plan to support it even after 138)

[leocg]

leocg Moderator Volunteer @andrew84 last edited by

@andrew84 It's a Chromium flag, probably doesn't have effect on Opera's PIP design.

[andrew84]

andrew84 @leocg last edited by

@leocg it's very bad. The PiP was not improved and the flag was also removed. Another one reason to stay away.

[MehrzadS]

MehrzadS last edited by

This problem has been reported since 2020 and it still persists. Trying to drag the scrollbar on the right drags the entire window. Ubuntu 24.04 on Wayland 1600x900 resolution, no fractional scaling.

[MehrzadS]

MehrzadS @andrew84 last edited by

@andrew84: All it takes is to change the event from mouse down to mouse click. But they won't do it; they don't care.

[andrew84]

andrew84 @MehrzadS last edited by

@MehrzadS If I don't mistake, the bug was introduced when the 'modular' design was introduced and the content border appeared. So when Opera One was announced, it means somewhere in 2023. At least on Windows.
Later they fixed it for windows.

*Another one bug was that mouse wheel didn't work while the cursor is far right (on the 1px content border). Later it was also fixed. But the same bug but for the left edge is still there.

[parduspars]

parduspars last edited by

My large font problem persists so I think I'll uninstall the developer version now. My brother else is using the stable version on my laptop. Sync was enabled in the dev version. Can I use different profiles in the same Opera or can I install two separate stable versions of Opera? I' m using Ubuntu 24.10 Thanks.

[MehrzadS]

MehrzadS @andrew84 last edited by

@andrew84 Sorry my memory is bad but I remember it's been there for a long time.

They must have patched it with an ad hoc solution. If you try to scroll the easy setup or a pdf file it still doesn't work even on Windows.

[andrew84]

andrew84 @MehrzadS last edited by andrew84

@MehrzadS said in Opera 121.0.5593.0 developer update:

If you try to scroll the easy setup or a pdf file it still doesn't work even on Windows.

A bit surprising after so much time, but indeed it doesn't scroll.

Edit: I did another one test. I filled the sidebar with icons (many workspaces) so it enables scrolling. It also doesn't scroll when the cursor is far left.
In old (pre One) Opera it works correctly for all the cases.

[andrew84]

andrew84 @andrew84 last edited by

@andrew84 Unfortunately, Edge also enabled the content border by default and removed option ('try new look') from Settings. But fortunately allows to disable it in flags so far.
Actually, the border there is even uglier than in Opera because it's ~4px wide. But I didn't notice issues with scrolling while the cursor is on that border,

[marinaz909]

marinaz909 Opera @andrew84 last edited by

@andrew84 Hello, we’re aware of this issue and it has been logged under DNA-121569. Thank you for your patience and feedback!

[deathcat]

deathcat last edited by

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"