Bug 114051
| Summary: | [CSS Filters] Accelerated SVG reference filters should not rely on FilterEffectRenderer to build the filter graph | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Max Vujovic <mvujovic> |
| Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | krit, sabouhallawa |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 68469, 114035 | ||
Max Vujovic
Note that only Chrome accelerates SVG reference filters right now, so this only causes problems there right now.
We should extract the SVG graph building functionality out of FilterEffectRenderer, and it should happen when we call RenderLayer::computeFilterOperations. FilterEffectRenderer is intended to render software filters and shouldn't be needed for accelerated filters.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Said Abou-Hallawa
FilterEffectRenderer was removed in r235630. Then was reintroduced for a different purpose in r264805. Then it was deleted in r286193.
Accelerated filters are implemented using CoreImage for CG. But it is limited and it is still an internal feature.