RESOLVED WONTFIX280958
[site-isolation] RenderLayerBacking::updateAfterWidgetResize needs to notify cross-process subframe RenderLayerCompositors of bounds changing 
https://bugs.webkit.org/show_bug.cgi?id=280958
Summary [site-isolation] RenderLayerBacking::updateAfterWidgetResize needs to notify ...
Matt Woodrow
Reported 2024-10-06 22:58:15 PDT
The code currently only works with in-process subframes.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2024-10-06 22:58:25 PDT
<rdar://problem/137406024>
Matt Woodrow
Comment 2 2024-10-06 23:01:36 PDT
Pull request: https://github.com/WebKit/WebKit/pull/34756
EWS
Comment 3 2024-10-09 15:37:18 PDT
Committed 284932@main (3f1856724b13): <https://commits.webkit.org/284932@main> Reviewed commits have been landed. Closing PR #34756 and removing active labels.
WebKit Commit Bot
Comment 4 2024-10-10 18:50:36 PDT
Re-opened since this is blocked by bug 281269
Matt Woodrow
Comment 5 2024-10-13 14:00:19 PDT
I reverted this because it causes visual rendering issues in http/tests/site-isolation/selection-focus.html, despite making the graphics layer dumps match. It looks like in the site-isolation case, the RenderLayer for the <iframe> creates a 'contents' GraphicsLayer, and the relevant offset is set on that (and that layer isn't included in the dump). For in-process iframes, there's no contents layer, just the child RenderView/RenderLayerCompositor, and we manually forward the offset down to it. I don't think there's anything to fix here, unless we really need the layer trees to be identical (which is nice for testing, but probably doesn't matter).
Note You need to log in before you can comment on or make changes to this bug.