Bug 222950 - <model>'s inner compositing layer is re-created every time it moves
Summary: <model>'s inner compositing layer is re-created every time it moves
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Tim Horton
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2021-03-08 15:52 PST by Tim Horton
Modified: 2021-03-09 13:58 PST (History)
4 users (show)

See Also:

Attachments
Patch (2.58 KB, patch)
2021-03-08 15:52 PST, Tim Horton 		no flags Details | Formatted Diff | Diff
Patch (2.86 KB, patch)
2021-03-08 21:11 PST, Tim Horton 		no flags Details | Formatted Diff | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Horton 2021-03-08 15:52:00 PST 
<model>'s inner compositing layer is re-created every time it moves
Comment 1 Tim Horton 2021-03-08 15:52:25 PST 
Created attachment 422629 [details]
Patch
Comment 2 Tim Horton 2021-03-08 21:11:25 PST 
Created attachment 422663 [details]
Patch
Comment 3 EWS 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].
Comment 4 Radar WebKit Bug Importer 2021-03-08 21:42:38 PST 
<rdar://problem/75202509>
Comment 5 Sam Weinig 2021-03-09 08:26:57 PST 
I wonder if we could test something like this?
Comment 6 Tim Horton 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 :)
Comment 7 Sam Weinig 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.