This is the latest update from the Chromium devteam bugtracker:
https://bugs.chromium.org/p/chromium/issues/detail?id=1068170#c249
Quoted:
Comment 249 by kbr@chromium.org on Wed, Apr 21, 2021, 3:31 AM GMT+10 (6 days ago)
Apple has confirmed that they have a fix in hand and that it's being considered for a forthcoming macOS software update.
Comment 250 by mark@chromium.org on Wed, Apr 21, 2021, 4:24 AM GMT+10 (6 days ago)
Status: ExternalDependency (was: Started)
Per comment 249, ->ExternalDependency, as this is awaiting a fix from Apple.
I believe the ball is squarely in Apple's court although we won't really know for sure due to their silence on this matter.
It has been 6 days since the above was reported (not an official Apple response, just relayed by the Chromium team). Has anyone received any macOS updates recently (Catalina, Big Sur?) that you can test?
Still getting blue glitches. Especially after waking device from sleep. Same story.
Also, echoing brain_'s comment that this is not only impacting Chromium-based software. I did a list of software impacted by this further up in this thread.
As a way to flatly reject Apple's claims that we should direct our issue towards Chromium / Google, the following can be a good series of tests anyone can do when the blue glitches appear:
- Launch Safari
- Go to menu Develop > Show JavaScript Console
- Select the Layers tab
- Blue glitches will get rendered in the Layers tab
Interestingly, for some content, it appears that Safari can overcome the blue glitches. I've opened up sites such as Canvas (an LMS used by many educational institutions) glitching hard on Chromium but not on Safari. However, the above JavaScript Console > Layers tabs will always trigger the glitch – please try and report here if you can.
On top of that, this webGL demo URL will always trigger the blue glitches for me, on Chrome, Safari AND Firefox:
https://threejs.org/examples/#webgl_animation_cloth
So, even if all browsers are historically Chromium-based, it does say a lot about the fact that many applications do rely on the framework. Which could mean more are going to experience a higher recurrence of such incidents. This is only going to get worse in terms of people reporting it, right?
My line of support to Apple tracking this case has stopped replying to me. Has anyone faced this same wall of silence in your support cases?