Opera 120 developer
-
DerSchlingel last edited by@pilis00 I was trying to use Vivaldi, but it has a lot of bugs of its own. And it's only Chromium 134 as well.
-
daria19 Opera last edited by
@ralf-brinkmann: Thank you for bringing this to our attention! We have this issue logged as DNA-121975 and DNA-121702, and our team is actively working on a fix. We appreciate your patience!
-
-
daria19 Opera last edited by
@derschlingel: We understand your concerns regarding Chromium version updates and appreciate your feedback. While our goal is to provide the best and most secure user experience, aligning updates with Chromium's release schedule can sometimes present challenges. Integrating a new Chromium version takes time as we thoroughly test and ensure compatibility with all of Opera's unique features and enhancements. Rest assured, our team is committed to delivering these updates efficiently while maintaining high standards of functionality and security. We value your insights and are continuously working on optimizing our update processes. Thank you for your patience and understanding.
-
-
-
Referenced by pilis00
-
vladbabinets last edited by
Here is the English translation:
"Thanks for the update. I saw a new 'clear history on exit' function in the flags, but as I understand it, it's not working yet. But I'm glad that it has appeared. I would also like to see a feature to summarize YouTube videos, like in Yandex Browser, and the ability to change the Speed Dial background in the pre-installed themes." -
marinaz909 Opera last edited by@vladbabinets Hello, and thank you for sharing your suggestions! We truly appreciate hearing your ideas, as it’s always helpful to know which features or improvements matter most to our users.
-
pilis00 last edited by
@pilis00 said in Opera 120 developer:
@DerSchlingel said in Opera 120 developer:
Only on Chromium 134? This most recent stable version of Chromium is already used in the current versions of Chrome, Edge and Brave.
So guessing, we're having a Opera 120 stable with Chromium 134, Chrome and the pack will already be on 137. I don't think that's very assuring, actually.Even worse is that, I noticed that from Chromium 133 or 134, there is a huge audio desync bug that affects all Chromium browsers:
https://issues.chromium.org/issues/404464587
https://community.brave.com/t/audio-desynchronizes-from-videos-if-i-move-to-other-tabs/605669/28
https://forum.vivaldi.net/topic/107532/audio-desynchronizes-from-videos-if-i-move-to-other-tabsThis bug was fixed in version of Chromium 136, but if Opera doesn't apply some fixes by themselves or something, users with stay with this annoying issue for likely 2-3 months until Opera stable reaches Chromium 136, in which this bug is fixed.
@marinaz909 will you do something on this before Opera stable reaches version 134? In Opera developer the issue is here.
-
ralf-brinkmann last edited byWhen I click on the padlock to the left of the address bar to check or change the page settings, I have difficulty reading the black text on the dark blue background.
W11x64, Operax64
-
pilis00 last edited by pilis00
@ralf-brinkmann I also reported this issue too, it annoys me as well. And it's also on the stable version!
But a there is a much bigger issue now affecting Opera:
@pilis00 said in Opera 120 developer:
@DerSchlingel said in Opera 120 developer:
Only on Chromium 134? This most recent stable version of Chromium is already used in the current versions of Chrome, Edge and Brave.
So guessing, we're having a Opera 120 stable with Chromium 134, Chrome and the pack will already be on 137. I don't think that's very assuring, actually.Even worse is that, I noticed that from Chromium 133 or 134, there is a huge audio desync bug that affects all Chromium browsers:
https://issues.chromium.org/issues/404464587
https://community.brave.com/t/audio-desynchronizes-from-videos-if-i-move-to-other-tabs/605669/28
https://forum.vivaldi.net/topic/107532/audio-desynchronizes-from-videos-if-i-move-to-other-tabsThis bug was fixed in version of Chromium 136, but if Opera doesn't apply some fixes by themselves or something, users with stay with this annoying issue for likely 2-3 months until Opera stable reaches Chromium 136, in which this bug is fixed.
-
burnout426 Volunteer last edited by
@pilis00 Looking at https://chromium-review.googlesource.com/c/chromium/src/+/6383839/2/media/filters/ffmpeg_demuxer.cc and https://chromium-review.googlesource.com/c/chromium/src/+/6383839/2/media/test/pipeline_integration_test.cc, it's a very simple fix.
-
pilis00 last edited by
@burnout426 said in Opera 120 developer:
@pilis00 Looking at https://chromium-review.googlesource.com/c/chromium/src/+/6383839/2/media/filters/ffmpeg_demuxer.cc and https://chromium-review.googlesource.com/c/chromium/src/+/6383839/2/media/test/pipeline_integration_test.cc, it's a very simple fix.
I know, but that depends to Opera if they want to add it.
At how easy is to fix, it's a super annoying issue. -
Referenced by pilis00
-
burnout426 Volunteer last edited by
@pilis00 The need for the patch is now tracked as DNA-122031 and someone is looking into it. No guarantees, but at least it's known.
-
-
-
-
pilis00 last edited by
@burnout426 how you managed to do that? I would be really curious to see the status of the bugs, especially as I did report a lot of them.
-
-
marinaz909 Opera last edited by
@ralf-brinkmann Hello! The issue is tracked as DNA-122053. Thank you for your feedback and patience.
