Opera 106 developer
-
beboss last edited by
For me personally it's really hard to find sometimes which is the active tab. It's not tab obvious even it's "highlighted"
-
MichaIng last edited byOkay regarding black render areas, the "Out-of-process 2D canvas rasterization" flag alone does not seem to be the issue. To eliminate them, I currently additionally disabled "Multithreaded UI Compositor" and "Main thread runs as compositing" and enabled "Override software rendering list". I will try to narrow it down to what is really needed. It is a bid difficult to effectively test, since those black areas do not always appear immediately but sometimes after a longer time while browsing different websites.
-
-
andrew84 last edited by andrew84
@kened In private mode it looks even worse.
In overall they made a weird 'improvement' regarding the tab highlighting described here https://blogs.opera.com/desktop/2023/10/opera-105-developer/
tab islands enhancement, improved tabs and bookmarks highlighting in dark mode,
When hovering by cursor tab is bright, but when activating the tab becomes dull. In my opinion it should be vice versa. https://forums.opera.com/post/329899
-
karen-arzumanyan last edited by
Cursor issue still not resolved
!
Detail: https://forums.opera.com/topic/66351/opera-103-0-4928-0-developer-update/14
The problem also exists on version 106.0.4971.0 -
MichaIng last edited by MichaIng
Narrowed it down: It is actually "Multithreaded UI Compositor" and "Out-of-process 2D canvas rasterization." which both cause the issue individually, even if the other flag is disabled, but also in combination. "Main thread runs as compositing" and "Override software rendering list" seem to have no effect on the matter, the latter of course in generally only matters if the own GPU is on this software rendering list, which seems to be not true for mine. opera://gpu/ shows:
Graphics Feature Status
- Canvas: Hardware accelerated
- Canvas out-of-process rasterization: Disabled (manually disabled via flag)
- Direct Rendering Display Compositor: Disabled
- Compositing: Hardware accelerated
- Multiple Raster Threads: Enabled
- OpenGL: Enabled
- Rasterization: Hardware accelerated
- Raw Draw: Disabled
- Skia Graphite: Disabled
- Video Decode: Hardware accelerated
- Video Encode: Hardware accelerated
- Vulkan: Disabled
- WebGL: Hardware accelerated
- WebGL2: Hardware accelerated
- WebGPU: Hardware accelerated
-
-
-
-
donq last edited by
@michaing said in Opera 106 developer:
Narrowed it down: It is actually "Multithreaded UI Compositor" and "Out-of-process 2D canvas rasterization." which both cause the issue individually, even if the other flag is disabled, but also in combination.
Same here - either flag alone didn't help. Disabling both seems workig so far.
This seems to be related to only very specific video hardware/driver - I have Intel onboard video on different PCs, but only one (older) is affected.
-
MichaIng last edited by
@donq It's strange: In the meantime the issue reappeared with those two flags disabled, just after a longer while. I disabled again "Main thread runs as compositing" and also "Accelerated 2D canvas" and "GPU rasterization", one by one after each did not help. Currently I do not face the issue, but I remember a little black glitch yesterday. I fail to derive a clear cause-and-effect, but it is more like the chances for the issue to appear, or better the time/actions it takes while using Opera before it appears, seem to increase when disabling the flags. If I change back all of them to default, very quickly vast parts of the screen/website turn black again.
So someone needs to dig into the depth of 2D compositing and how these flags can affect it in a way that these black areas appear more or less often, but without any flag being the only and definit cause of or solution for it
. If someone has an idea how to debug, I am open to help, but I am out of ideas. -
-
Locked by
leocg
