Opera 114.0.5242.0 developer update
-
MichaIng last edited by@burnout426 Thanks, deleting "Login Data" and journal indeed worked. The meta data of old and new file are exactly the same. So this means the format of that file has changed between Opera versions and no migration is done? Would be great to have a way to migrate the old "Login Data", would be absolutely essential at least in stable release, IMO. Could be quite a disaster for many users, it is half one for me.
-
burnout426 Volunteer last edited by
@michaing Not sure if the format changed a bit or if the key in the "Local State" file that's used to encrypt the "Login data" file changed for some reason. With the latter, it causes Opera to not be able to read and write to the file because it doesn't have the old key to decrypt it.
Sometimes (not always), a change of your Windows user account password can cause that. Sometimes (not always) a Windows update can trigger a change of key. Other times it can be corruption. Other times, it's something with Opera's updater that boogers up things for some users. No clue.
-
MichaIng last edited by
@burnout426 Ah yes that makes sense. Since it clearly broke with 2nd last Opera developer update, that is the culprit, not Windows update or user password change (which did not happen). I hope such is prevented in Opera stable. Using a developer version as production system could be called own fault :).
-
burnout426 Volunteer last edited by
@simcard78 Ah, very simple to reproduce once I enabled "Enable tab scrolling when many tabs are open" at the URL
opera://settings/userInterface. -
kmielczarczyk Opera last edited by@burnout426: Thanks a lot. Tab scrolling was a key. We've got it and reported. Our developers will take care of this now. Thanks a lot for your help.
-
SiMcarD78 last edited by
@burnout426: Thank you! I don't actually use this feature so I can disable it as a workaround for now.
-
rick2 last edited by
@kmielczarczyk Yes, and sorry I came off too harsh but I was really mad at the current situation with Opera (the Aria icon is another pain point).
First of all, I prefer scrolling Tab Strip and have Tab Islands and Tab grouping disabled in Opera Beta.
Still, whenever I drag a tab on top, a new group/island gets created, and usually tha Tab Strip gets scrolled to another place (so I lose focus on the just dragged tabm which is anothe annoyance).But the whole Tab area is a mess currently. Dragging a tab in Beta 113.0.5230.18 for instance can only be done if you are careful not moving the mouse outside the Tab Strip, or Opera instead resizes itself.
That also prevents fomr detaching a tab from a window.
Then there's the click on the active tab to mve to the top, which doesn't distinguish between a click and a drag and always goes to the top unconditionally.
There might be more but that is the most annoying thing to me.
(I also have more issues lately but I'm not sure those are Opera's faults or my distro/desktop's bugs)
-
rick2 last edited by
BTW, this is on Fedora 40 KDE, opera-beta-113.0.5230.18-0.x86_64 installed via the RPM repository.
-
-
andrew84 last edited by
@kmielczarczyk So this is an issue or design? If this is by design, what for was the fix?
-
-
-
-
-
burnout426 Volunteer last edited by
@tastodd Long story short, that bug was to fix some issues with the context menus not matching the design (that must be a newer design that doesn't match how things were perfect in Opera 111). So, we can ignore whether that bug is fixed or not.
Opera knows that we're questioning the new design itself and they're looking into it at least.
Maybe the new design was only tested with high-resolution, huge displays where it looks great there. Not sure.
-
andrew84 last edited by
@burnout426 Personally, I understood that whatever they do recently: designing smth new, redesigning, refreshing the redesign, it won't work as smooth as it worked in pre-One versions.
-
Locked by
leocg
