Summary: | Store event region on non-composited frames | ||
---|---|---|---|
Product: | WebKit | Reporter: | Daniel Bates <dbates> |
Component: | UI Events | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Normal | CC: | koivisto, simon.fraser, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Local Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: |
https://bugs.webkit.org/show_bug.cgi?id=210278 https://bugs.webkit.org/show_bug.cgi?id=210041 https://bugs.webkit.org/show_bug.cgi?id=209888 https://bugs.webkit.org/show_bug.cgi?id=210216 |
Description
Daniel Bates
2020-04-09 16:27:39 PDT
Note that we cannot depend on checking RenderView::needsEventRegionUpdateForNonCompositedFrame() in RenderWidget::paint() since it could be have been set by a deep nested non-composited child frame and an intermediary child frame along the path may have had its layout dirtied. That is why we check needsLayout(). Eventually the needsEventRegionUpdateForNonCompositedFrame() bit will be serviced (and turned off) once all frames along the path to the originally requesting frame lay out. Or figure out how to composite frames without a massive memory regression. |