Introducing Opera 102
-
auxce last edited by
Click on a tab to get to the top of a page doesn't work after moving back in page history of that tab.
-
OperaUserPT last edited by
After the update, every thing is gone: speedial, bookmarks, extensions, settings, sidebar configuration ...
-
tastodd last edited by
Terrible Opera update . Not only did Opera freeze after the update and it didn’t load for a long time, but all passwords, tabs were deleted, speed dial was cleared. This is not allowed in the stable branch.
-
thelittlebrowserthatcould last edited by
Good to have tab-scrolling back, and the text labels for workspaces when moving tabs to them.
I have 12 workspaces. Setting up an additional one deletes one of the earlier ones, with its collection of tabs, with no warning. Naturally, I'm not inclined to test this new feature any further.
-
A Former User last edited by A Former User
Thank you for this great update and the polishing. It looks great. The only thing I'm missing - still - is the speed dial button (home button rsp.) next to the addressbar.
-
thelittlebrowserthatcould last edited by
@adam1709: have you enabled Scrollable tab strip in opera://flags and Settings: User interface? A scrollbar should appear at the top of the screen, when the tab strip gets overcrowded.
-
francehelders last edited by
I upgraded to Opera 102 on a Windows machine and all session is gone. Tabs, passwords, history, everything.
My laptop runs Linux. I'm waiting next Opera 102 release with fixes. Only after that i will update Opera on my laptop.
Very inconvenient! -
adam1709 last edited by
@thelittlebrowserthatcould I had previously enabled it in opera://flags, but this feature worked badly, so I disabled it. I read that it is supposed to appear in version 102 and I still don't see it. And normally in the settings I don't see this option.
-
thelittlebrowserthatcould last edited by
@adam1709: Did you re-start Opera after enabling the setting in opera://flags? You are correct, it isn't shown in Settings with the flag disabled.
-
paul-durham last edited by
@olifant: As per a recent post of mine in the Opera Blog & in the Forums, Opera One feels far from production-ready. There are just so many serious failures. Aside from beings secure, the next thing users expect is that the product doesn't lose their tabs & information. @kornelia Mielczarczyk is the Product Quality & Launch Coordinator - please will you provide feedback on the wide-spread issues plaguing Opera One users, as well as Opera's plan to rapidly resolve them.
-
adam1709 last edited by
@thelittlebrowserthatcould Of course I then restarted. Whenever you change the flag it displays a message like this. I don't move the flag because it's probably still malfunctioning. It was supposed to be normal as I understood in version 102 as it was before version 100, and it isn't....
-
plovec last edited by plovec
@paul-durham: After the "Restart to update Opera to a newer version" I waited for 31 minutes while Opera incessantly worked on disk... I think you are right since I have all my speed dials restored.
-
paul-durham last edited by
@plovec: It is interesting to see others also had a very long delay before Opera opened after the update. This appears to be another issue with the stable release.
-
genegold last edited by
Win 10 Pro x64 22H2. 102 is not ready for release. It returned profile error message and then wouldn't start past 'O' sound screen. On reboot, 9 extensions either showed error or "maybe corrupt" messages. Had to run system restore.
-
raphaelbm last edited by
The announcement of 102 at https://blogs.opera.com/desktop/category/stable-2/#:~:text=Stable update
shows:
Stable
Introducing Opera 102
August 23rd, 2023However, the version is not shown. I have to go all the way to the changelog to discover the version is 102.0.4880.16
Please fix these announcements to mention the version at the same time as the announcement. You do this at Updates but not when announcing a new major level. Why do you do this? Stop it... Please be consistent.
This is a bug in the blog post. This is not a bug in the product.
Thx Raphael