Hello @pixmen!
Last week, we started receiving reports identical to yours, and we started investigating, since we didn’t change anything substantial in our rendering that could be affecting Windows users.
In the end, it seems related to how Chrome (and Chromium-based web browsers like Edge) handle hardware acceleration on PC. As a workaround, please ask anyone with this issue to deactivate hardware acceleration in Chrome. This guide outlines the steps for doing it in Chrome.
The issue seems to be on Chrome’s side and its a bug already acknowledged by them. Google has already assigned max priority to it and is working on a solution. See the issue in the Chromium ticketing tool here.
I’m afraid that now it’s a matter of keeping the hardware acceleration deactivated, or using Firefox (which is the only widely used browser that doesn’t use Chromium), and wait for Chrome to release the update to Chrome 143, which seems to be the target version according to the thread linked above.
I hope this helps!