Bug 272364

Summary: REGRESSION(??????@main): [GTK] Regression with webview background color rendering and DRI
Product: WebKit Reporter: Philip Chimento <philip.chimento>
Component: WebKitGTKAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: bugs-noreply, mcatanzaro
Priority: P3 Keywords: Gtk
Version: Other   
Hardware: PC   
OS: Linux   
Attachments:
Description Flags
Sample program
none
Video showing glitchy behaviour none

Philip Chimento
Reported 2024-04-08 18:10:20 PDT
Created attachment 470827 [details] Sample program The attached sample program demonstrates a web view in GTK 3 that is supposed to be transparent, i.e. renders the HTML on top of the background color of the GtkWindow that the web view is placed in. At some point between GNOME 43 (webkit2gtk-4.1 2.40.5) and 44 (webkit2gtk-4.1 2.42.5) there was a regression that caused this to stop working. Instead of the background color of the window, the contents of the screen behind the window show through, but in a glitchy way. However, if the DRI permission is disabled, the glitch is gone, and the behaviour is as expected. See the attached video where I executed the sample program in subsequent flatpak runtimes: - org.gnome.Platform//43 with --device=dri - works as expected - org.gnome.Platform//44 with --device=dri - glitches - org.gnome.Platform//44 without --device=dri - works as expected The equivalent program using GTK 4 and webkitgtk-6.0 doesn't seem to exhibit this problem.
Attachments
Sample program (964 bytes, text/x-csrc)
2024-04-08 18:10 PDT, Philip Chimento
no flags
Video showing glitchy behaviour (1.45 MB, video/webm)
2024-04-08 18:11 PDT, Philip Chimento
no flags
Philip Chimento
Comment 1 2024-04-08 18:11:09 PDT
Created attachment 470828 [details] Video showing glitchy behaviour
Michael Catanzaro
Comment 2 2024-05-07 10:28:56 PDT
I can reproduce. I built 260527@main (2.40 branchpoint) with intention of bisecting this, but the bug occurs there exactly the same for me. My assumption is that something else in the GNOME runtime changed between 43 and 44. Unfortunately it's much harder to guess what it could be since we took so long to notice this regression.
Note You need to log in before you can comment on or make changes to this bug.