Bug 222950

Summary: <model>'s inner compositing layer is re-created every time it moves
Product: WebKit Reporter: Tim Horton <thorton>
Component: New BugsAssignee: Tim Horton <thorton>
Status: RESOLVED FIXED    
Severity: Normal CC: dino, sam, simon.fraser, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch
none
Patch none

Tim Horton
Reported 2021-03-08 15:52:00 PST
<model>'s inner compositing layer is re-created every time it moves
Attachments
Patch (2.58 KB, patch)
2021-03-08 15:52 PST, Tim Horton
no flags
Patch (2.86 KB, patch)
2021-03-08 21:11 PST, Tim Horton
no flags
Tim Horton
Comment 1 2021-03-08 15:52:25 PST
Tim Horton
Comment 2 2021-03-08 21:11:25 PST
EWS
Comment 3 2021-03-08 21:41:28 PST
Committed r274136: <https://commits.webkit.org/r274136> All reviewed patches have been landed. Closing bug and clearing flags on attachment 422663 [details].
Radar WebKit Bug Importer
Comment 4 2021-03-08 21:42:38 PST
Sam Weinig
Comment 5 2021-03-09 08:26:57 PST
I wonder if we could test something like this?
Tim Horton
Comment 6 2021-03-09 11:41:57 PST
(In reply to Sam Weinig from comment #5) > I wonder if we could test something like this? I wasn't sure how, without doing something highly overkill like internals API that vended layer pointers or something :)
Sam Weinig
Comment 7 2021-03-09 13:58:19 PST
(In reply to Tim Horton from comment #6) > (In reply to Sam Weinig from comment #5) > > I wonder if we could test something like this? > > I wasn't sure how, without doing something highly overkill like internals > API that vended layer pointers or something :) Yeah, looking at the underlying issue being pointer comparison, it does seem tricky.
Note You need to log in before you can comment on or make changes to this bug.