| Summary: | [GTK] Web view misrenders systematically with GTK 4 port | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | vanadiae <vanadiae35> | ||||||||
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> | ||||||||
| Status: | RESOLVED FIXED | ||||||||||
| Severity: | Normal | CC: | bugs-noreply, mcatanzaro, vanadiae35 | ||||||||
| Priority: | P2 | ||||||||||
| Version: | Other | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Linux | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 466105 [details]
screenshot of duckduckgo.com
Hm, the radeon kernel module is atypical. Could you copy/paste webkit://gpu and attach it here, please? Also, does WebKitGTK 2.40.x work? Try with either Flathub or a distro packaged version. Created attachment 466109 [details]
webkit://gpu
I will try downgrading the GNOME SDK to have earlier WebKitGTK. Hmm that's embarrassing. At some point I updated and the bug was there, then it disappeared and reappeared afterwards, staying for good. But now I just updated again the GNOME SDK (to downgrade it later) and the bug is gone. Maybe https://gitlab.gnome.org/GNOME/gnome-build-meta/-/commit/3d6fb3e82c36203986151e3873abdeb71180a324 is to do with it? Or it was just fixed as part of another commit between 2.41.2 and 2.41.3. I guess that's good then :). For now I'll close the issue, and eventually (but hopefully not) will re-open the issue, if that's even possible with bugzilla. |
Created attachment 466104 [details] screenshot of gnome.org Versions & informations: - Tested in Epiphany (GNOME Web) nightly and GNOME Builder nightly, using WebKitGTK 2.41.2 (webkitgtk-6.0, GTK 4) - Wayland with radeon kernel module (not the newer amdgpu, if that's of any importance) on GNOME All pages get rendered wrong but still respond to inputs: the rendered page changes when scrolling, links can be hovered and clicked just fine. Something else interesting is that the web inspector renders without any issue contrary to the page itself. The best way to understand the issue is to see it, so see the attachments for screenshots. The issue did not happen a few updates ago (still with GTK 4), but I wouldn't be able to tell when it broke exactly. Let me know if there is any other information that you need or things I can test to help figure out the exact issue.