[Webkit-unassigned] [Bug 261273] New: REGRESSION(262812 at main): No render updates after cross origin history navigation
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Sep 7 05:32:46 PDT 2023
https://bugs.webkit.org/show_bug.cgi?id=261273
Bug ID: 261273
Summary: REGRESSION(262812 at main): No render updates after cross
origin history navigation
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Keywords: Gtk, Regression
Severity: Normal
Priority: P2
Component: WebKitGTK
Assignee: webkit-unassigned at lists.webkit.org
Reporter: cgarcia at igalia.com
CC: bugs-noreply at webkitgtk.org
This regressed in 262812 at main because we moved the code to enter AC mode when always compositing to the DrawingArea constructor to make sure the UI process starts receiving IPC messages for the new drawing area as soon as possible after a drawing area switch due to cross origin navigation. The problem now is when going back after a cross origin navigation because there's a display refresh monitor switch too, but to create the proper display refresh monitor we need an already created drawing area, since WebChromeClient::displayRefreshMonitorFactory() returns the WebPage drawing area, not yet set during its constructor. So, we need to enter AC mode right after the drawing area is created instead of in the constructor to ensure the right display refresh monitor is created. This doesn't fail in GTK3 because we create a DisplayRefreshMonitorGtk, but that's not the right one either, since it's expected to be used only for non-AC mode.
--
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/20230907/c4f59feb/attachment.htm>
More information about the webkit-unassigned
mailing list