Opera 137 Stable
-
Opera Comments Bot last edited byHello! We’ve rolled out a new Opera Stable 137 release with a Chromium bump and several stability fixes. On top of that, we’ve enabled #opera-one-react-settings by default: refreshed Settings experience, rebuilt in React and lightly redesigned along the way. Core Tabs Early Bird features: You can find the full list in the changelog. Happy browsing! […]
Read full blog post: Opera 137 Stable
-
-
andrew84 last edited by andrew84
You have broken (removed intentionally) the 2nd click for the 'scroll to top' feature but at the same time still didn't fix the bug when page scrolls to top while moving tabs.
The bug persits more than 3 years. -
andrew84 last edited by andrew84
- I couldn't yet to reproduce the bug regarding the 'invisible area' resulting in moving entire window > https://forums.opera.com/post/410412
But I can easily reproduce the bug from the same thread while the cursor is far right or far left. https://forums.opera.com/post/410464
*The both bugs are still reproducible in Developer.
- You also didn't fix the hidden tabs and new tab button after expanding tab islands. https://forums.opera.com/post/409807
-
max1c last edited by
Fluent Scrollbars have been removed and I don't see an option for Overlay Scrollbars. How do I hide scroll bars now???
-
oP2 last edited by
Lucid mode causes a critical bug which hangs the browser. If you put any other site in PiP then go to youtube and start a video and click on the running PiP the browser will hang. The only way to fix is either relaunch or kill the right process from task manager. The same is going on with Dev build
-
danstudio last edited by
The BUG-25876 issue is still there!
It is also known as BS-92008, BUG-24931, and BUG-27619.
https://forums.opera.com/topic/89379/devtools-does-not-resize-the-page-viewport-after-navigationLike 2 years already (if not more).
This is extremely inconvenient for developers.Sometimes it is (partly) fixed after Chromium update, but then you reapply like some your "features" over and here we go again..
Shame on you! -
-
-
andrew84 last edited by
Despite of deprecating Beta channel and implementing the EarlyBird feature (as I understand it was made to keep the Chromium version more updated) the Stable version (just released) is still on 153 ver. while Edge Stable is already on 155.
Opera Dev version is also still on 153.
So the result is that Stable version is almost = Developer version (with all the ensuing consequences) but still 2 versions behind actual chrome version. -
leocg Moderator Volunteer last edited by
@andrew84 It's been a while that Opera stopped using Developer version of Chromium on Opera Developer and now uses stable versions of Chromium on both Opera Stable and Opera Developer.
Seems to me that it was a deliberated decision, to make development easier.
-
andrew84 last edited by
@leocg said in Opera 137 Stable:
to make development easier
Yes, maybe.
But it seems it didn't if the chrome's version is also still not actual, as before. -
burnout426 Volunteer last edited by
@andrew84 Chromium changes break Opera's patches to Chromium and break Opera's features quite frequently. It's way worse when Opera takes in a new major version of Chromium. Building a browser and developing features on top of an ever-changing Chromium that you don't control often means regression city and actual breakage.
Basing Opera on the extended stable channel of Chromium for both Opera Stable and Developer makes things easier for Opera and keeps them more stable. It does suck though for those that want the latest stable Chromium for Opera Stable and the bleeding edge Chromium for Opera Developer.
As you've noticed, Opera already has enough UI regressions for example that are probably not Chromium-related to deal with.
It's not that Opera can't do things like desired. They did it before. But, they've made an active decision not to.
-
