Opera 69.0.3630.0 developer update
-
ralf-brinkmann last edited byChromium bug not fixed. www.nikon.de still not reachable.
W10x64, Operax64 -
-
james438 last edited by
Whoa! Videos are working again! They were not down on all sites, but on some, like foxnews.com, they were dead.
-
james438 last edited by
@james438: After an update to Opera a few updates ago videos on Foxnews all stopped working. This update also affected Opera Developer. After this most recent update to Opera, the videos now work on Developer and Beta. I believe that this is due to the update to Chromium, but I thought that the different versions of Opera used a different Chromium engine. Am I incorrect? If so, how are the different versions linked so as to cause videos to be broken across all versions and then to be fixed across all versions?
-
-
andrew84 last edited by
bug:
In Dev/Beta the toggle in Extensions 'Details' doesn't work.
*None of the bugs from this list was fixed.
https://forums.opera.com/post/202034 -
james438 last edited by
@tina: Actually, it works fine with adblocker on; just needs to be tweaked a bit. I have Windows 7. The issue that I was experiencing as well as the recent fix which occurred across Opera Developer and Stable at the same time was with all of the add-ons disabled. In the case of Opera Developer the add-ons were not installed. I try to keep Opera Developer in the original freshly installed state. Regarding the videos on foxnews.com I even disabled the built in ad blocker.
Not sure if that helps, but thanks for the response!
-
james438 last edited by
@james438: small addendum. It looks like my adblocker is more than a little modified. Apparently, I am only using custom filters ;).
Regardless, my main curiosity is if the different Opera browsers are all linked so as to cause videos to all stop working and then all start working after either browser is updated. If they are linked, then how are they linked? Is it the Chromium engine itself? I thought that the Chromium engine for each version of Opera was independent.
-
-
tina Opera last edited by
@james438 I'm not sure that get your question correctly, but if you have the same custom lists in Adblocker enabled ( e.g. some country list) and it was the reason why video doesn't work you; then you got an update of this adblocker rules - and video start working. Nothing connecting to engine in that case.
-
A Former User last edited by
@tina This bug is not in
opera://extensions. You should go to the "Details" and try there.
The bug is present in Opera Beta/Dev, Win 7x64. -
-
-
-
andrew84 last edited by
@ralf-brinkmann: Chromium's bug as it seems.
https://bugs.chromium.org/p/chromium/issues/detail?id=930812#c7 -
ralf-brinkmann last edited by
@andrew84 Yes, that's what I thought and wrote in my comment. It works in the actual Vivaldi, but not in Google Chrome Developer. I don't know why it works on @thortik's computer. Maybe he has disabled chrome://flags/#post-quantum-cecpq2.
-
james438 last edited by
@tina: The videos stopped working in Opera Developer and Opera Stable at the same time and then started working in both versions at the same time even with all add-ons disabled or uninstalled using Opera Recovery.
It is because the error and fix happened with both browsers at the same time that it led me to suspect that there is a core program or engine that both browsers are using simultaneously. Is this correct?
-
thortik last edited by
@ralf-brinkmann There is no such flag in Opera and Vivaldi. She is only in Chromium. Despite this, this function is enabled and the site still opens without problems. This site works for me in all my browsers.
I think this is the problem of the your internet-provider or system configuration, not the browser. -
-
ralf-brinkmann last edited by
@thortik There IS such a flag. I copied the flag from my browser in "opera:flags" and this is not new. Starting in an older version of 68.x we had the same problem. The behaviour is the same in Google Chrome Version 82.0.4083.0 dev (64-Bit). Vivaldi uses an older version Chrome/81.0.4044.66.
W10x64, Operax64
Didn't notice that this happens inside 'Details'. listener not defined for Toggle. Reported as DNA-85212
