Opera 110
-
antonio1678 last edited by leocg
@leocg: Yes that sounds cool. So tell me, where are the backport entries for the 9 missing high and critical security fixes that appeared with the subsequent Chromium versions (including two 0-days with active expoilts in the wild) in the changelog? Or was your answer just to draw attention away from Opera letting their users down?
-
antonio1678 last edited by
@adam1709: CVE-2024-4671 is so last week. There is a new zero day as of late yesterday. CVE-2024-4761. Yes look carefully at that number it is different https://chromereleases.googleblog.com/2024/05/stable-channel-update-for-desktop_13.html
It seems like so far only Chrome and Vivaldi have the fix for that one.
-
antonio1678 last edited by
@leocg: I notice you hand waved past the answer that was required, choosing only to talk about Chromium versions varying between browsers. I'll go straight to the point, are the security fixes found in the latest Chrome here or not?
-
adam1709 last edited by@antonio1678: Well, Opera before it gets to more than 200 is still a few weeks away. It just started at 62
-
adam1709 last edited by
The tab bar (scrolling) still does not open on the active tab, and every time it starts the far left.... how long can you wait until this is taken care of?
-
-
-
leocg Moderator Volunteer last edited by
@antonio1678 I'm an user like anyone else, I just said what usually happens.
I don't know if those security fixes from Chromium were already incorporated in Opera.
And, honestly, I not that worried about that.
-
thelittlebrowserthatcould last edited by@adam1709: do you mean when Opera starts up? When moving between workspaces, the last-used tab is where I land, although the scroll-bar is randomly positioned. I would prefer this: https://forums.opera.com/topic/70564/tab-scrolling-set-a-default-option
-
tastodd last edited byWhen playing a YouTube video in full screen, gray curves are visible in the corners.
Most likely this bug is related to the#ui-compositor-multithreadedflag -
iosaddict 0 last edited by
@leocg If only they care to mention them in their blog posts. This is seriously unacceptable. I mentioned this a couple of time in the past only to get downvoted by you. Thankfully this time around a number of people are care to bring this out again and it is quite concerning the way Opera is dealing with security vulnerabilities.
-
leocg Moderator Volunteer last edited by
@iosaddict-0 Like I said, when there is a release with really important security fixes, they usually mention it in the blog post and/or in the changelogs.
-
andrew84 last edited by andrew84
@tastodd I don't know what is related to (I thought this is content's border some bug again) but I reported the same a month ago in dev thread
https://forums.opera.com/post/348059 -
adam1709 last edited by
@thelittlebrowserthatcould: That's what I mean right from the start of the browser. I don't use contexts - I only have one. I have multiple tabs and the bar is always the far left after launch, even though the active tab is somewhere in the middle or at the end on the right.
This used to work normally, it moved automatically to where the last active tab was. There was a longer pause when they took it away and when it came back it hasn't worked like it used to since.
I read what you linked. I didn't know you could click on options there, but they don't make sense because as I understand it they are one-time and there is no option to move to the active card - just click ctrl+tab twice to move to the active card. But I fully agree with it. I can't fit in my head that they neglected it like that. In Firefox it works wonderfully. -
kmielczarczyk Opera last edited by
@adam1709: Hi, in this build, a 0-day fix from Chromium has been included, the changelog has been updated. The new intake with Chromium version 124.0.6367.202 is in progress for further updates.
-
adam1709 last edited by
@kmielczarczyk: That's good, it was missing from the beginning. However, what puzzles me is why 124 came out with version 62 from a few weeks ago?
-
-
antonio1678 last edited by
@kmielczarczyk: Which of the two 0-days since the .61 release would that be, given there is no CVE listed in the change log (please fix that) and these have been two separate 0-days? Is it "High CVE-2024-4671: Use after free in Visuals"? Ok, then how about the other 0-day, "High CVE-2024-4761: Out of bounds write in V8"? Is that also fixed and you forgot to list it? And what about all of these security fixes that are not listed in your change log? Do you have them as well? Why would you back port these when you could just move up the Chromium branch and get them all more easily than needing to back port?
High CVE-2024-4558: Use after free in ANGLE
High CVE-2024-4559: Heap buffer overflow in WebAudio
High CVE-2024-4331: Use after free in Picture In Picture
High CVE-2024-4368: Use after free in Dawn
Critical CVE-2024-4058: Type Confusion in ANGLE
High CVE-2024-4059: Out of bounds read in V8 API
High CVE-2024-4060: Use after free in DawnI don't want to call you a liar but what you are saying makes little sense and hence I am struggling to believe it. Nonetheless, if you have fixes for all of these… please update the change log.
-
-
tastodd last edited by tastodd
I don't know what is related to (I thought this is content's border some bug again) but I reported the same a month ago in dev thread
https://forums.opera.com/post/348059I hope the Opera team @kmielczarczyk will somehow respond to this problem
Because for the stable version it's kind of ugly
