Bug 112830
Summary: | [CSS Filters] Remove HAVE(COMPOSITOR_FILTER_OUTSETS) when all platforms' compositors can compute filter outsets | ||
---|---|---|---|
Product: | WebKit | Reporter: | Max Vujovic <mvujovic> |
Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | achicu, ahmad.saleem792, bfulgham, krit, simon.fraser, zalan |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Bug Depends on: | 109098 | ||
Bug Blocks: | 68469 |
Max Vujovic
In bug 109098, I'm planning to add a flag HAVE(COMPOSITOR_FILTER_OUTSETS). We use this flag to decide whether to include filter outsets in composited layer bounds. Right now, only Safari's CoreAnimation compositor computes its own filter outsets. Thus, we shouldn't inflate layers for Safari.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Ahmad Saleem
We don't have 'COMPOSITOR_FILTER_OUTSETS' in WebKit source (searched using Searchfox.org on WubKat):
https://searchfox.org/wubkat/search?q=COMPOSITOR_FILTER_OUTSETS&path=&case=false®exp=false
^ It is not present, so removing this won't be possible.
Can we close this?
Simon Fraser (smfr)
Yes