Bug 241777 - TextureMapperLayer::computeOverlapRegions doesn't need to use m_state.contentsRect
Summary: TextureMapperLayer::computeOverlapRegions doesn't need to use m_state.content...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Platform (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-19 23:52 PDT by Fujii Hironori
Modified: 2022-06-20 00:16 PDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fujii Hironori 2022-06-19 23:52:47 PDT
TextureMapperLayer::computeOverlapRegions doesn't need to use m_state.contentsRect

computeOverlapRegions has the following code.

>    if (m_backingStore || m_state.masksToBounds || m_state.maskLayer || hasFilters())
>        localBoundingRect = layerRect();
>    else if (m_contentsLayer || m_state.solidColor.isVisible())
>        localBoundingRect = m_state.contentsRect;

But, I don't know why m_state.contentsRect is used.
It was added by 129278@main (Bug 110762).
Comment 1 Fujii Hironori 2022-06-20 00:16:25 PDT
It might be for content layers with padding and transparent background.