@sgunhouse Bollocks. It's not "hardware dependent" when problem all of a sudden happened with Opera update across various hardware from crappy integrated Intel graphics to top of the line GTX 1080Ti cards. And it's not even only happening on webpages, it's happening within Opera components themselves. I was just editing a bookmark and the text in bookmark name field was flashing and sperging like we've reported it already. So, clearly Opera team broke something and has nothing to do with our systems or configurations we have.

Hardware dependent means that it only occurs on some hardware - which it does. That is not saying it is caused by the hardware. But if they don't know what hardware is required in order to reproduce the bug they won't be able to see the bug and will never know if something they try actually fixes it.

If you're not interested in seeing a fix, just keep ranting. Otherwise tell them something that might help them identify it.

So, I guess this is the moment where a random nobody (me) needs to teach actual developers how to fix things in their own program...

Instead of waiting months for people to post obvious things like the fact it appears on ALL NVIDIA and Intel GPU's (still waiting for mystery AMD users to show up, shall we wait for couple more months?) and apparently ALL Windows 8 and 10 versions starting with Opera 56, they could backtrack through Opera versions to the version which wasn't doing this (we have a rough timeframe and even version reports, the first Opera 56 build), read the changelogs what they changed back then, which may have caused this problem in that version and start from there? Just pointing out the Jupiter sized elephant in a room... When you know what was the exact version that started doing this, but one version back didn't, you literally just compare the changes done between the two and you'll find the problem. But hey, what do I know about the very basics of debugging stuff...

You know that they probably have been doing it already, right? And maybe they couldn't (easily) reproduce the problem, so they may haven't been able to narrow down in which build the issue started to compare anything.

When I try to update my Acer laptop using the Intel Assistant I get this error:

A customized computer manufacturer driver is installed on your computer. The Intel Driver & Support Assistant is not able to update the driver. Installing a generic Intel driver instead of the customized computer manufacturer driver may cause technical issues. Contact your computer manufacturer for the latest driver for your computer."*

So I've got my serial number and checked Acer web site support. It seems I have the latests "customized" driver version provided by Acer.

When I try to update my Acer laptop using the Intel Assistant I get this error:...

Yeah, the intel drivers are generic, but they might work better. You have to ignore that warning or uninstall your current drivers first to use the ones directly from Intel. They could work worse as said, but there's only one way to find out.

Can you download the installer for 56.0.3051.31, launch it, click "options", set "install path" to a folder on your desktop, set "install for" to "standalone installation", install and try in that Opera to make sure?

@derloopkat To get around that you need to go into the device manager, manually update the driver, choose "Have Disk", then point it to an extracted version of that driver. (Use 7-zip and right-click -> Extract the Intel driver update.) Once you replace the OEM specific driver with a generic intel one, you can install it properly immediately after. I did that to an old HP laptop a while back, and saw WEI scores jump from like 4.9 to 5.4. What a difference an up to date graphics driver makes.

That said, guess why I am here?

Flickering crazy selection crap (up to 4 different shades/colours jostling and jumping around in the background as I type) on:

Win10 x64 1803
GTX 1070
391.35

I typically have at least two or three web browsers open at once, and also office software like LibreOffice.

I'm testing on a Win10 x64 laptop with an Intel n4200 that has an HD 505 GPU and can confirm the issue,

As in, it works fine in the last Windows build before which is 56.0.3051.31?

The issue is still in that build too. I'm going to keep trying previous builds to see if I can find out when the issue started exactly. However, with Opera Developer build 58.0.3134.0, I can't reproduce the problem. So, maybe the issue is already fixed.