Bug 241777
| Summary: | TextureMapperLayer::computeOverlapRegions doesn't need to use m_state.contentsRect | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Fujii Hironori <fujii.hironori> |
| Component: | Platform | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | ||
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Fujii Hironori
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).
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Fujii Hironori
It might be for content layers with padding and transparent background.