[Webkit-unassigned] [Bug 228268] [GTK4] [REGRESSION] Rendering on Nvidia is terribly broken, almost a blank screen

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Jul 3 09:45:53 PDT 2022


https://bugs.webkit.org/show_bug.cgi?id=228268

--- Comment #17 from Emil Sayahi <limesayahi at gmail.com> ---
Created attachment 460640

  --> https://bugs.webkit.org/attachment.cgi?id=460640&action=review

Screenshot showing correct rendering in other browser

This is Reddit in Google Chrome, as a point of comparison to show how bright WebKitGTK still appeared, even when things were made visible with the switch to `libadwaita`'s forced dark mode.

I tried taking a screenshot in pre-GTK4 GNOME Web instead of Google Chrome, but it appears running my own browser causes the WebKitGTK component to become non-functional in GNOME Web until I restart my PC. This is true in the reverse—when, last night, I switched my browser to `libadwaita` (it was already using GTK4, FYI) the WebKit component decided to stop working completely, spitting out errors in the terminal, while GNOME Web operated fine. This remained the case until I restarted my PC this morning and attempted running my own browser again, when it started magically working without any code changes, but apparently caused GNOME Web to break.

If you want to tinker around with my GTK4 + libadwaita + webkit2gtk-5.0 web browser to debug things yourself, the source code is here: https://github.com/Dirout/oku/ (latest commit is https://github.com/Dirout/oku/commit/dda8ee0c11e520a78c69e77e0ba00726bb032436 as of posting this comment).
To run it, install the Rust compiler toolchain and run `cargo run --release` inside the source code directory.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220703/098eb209/attachment-0001.htm>


More information about the webkit-unassigned mailing list