Closed Bug 1455427 Opened 7 years ago Closed 2 months ago

SVG filters on HTML content is a bad time

Categories

(Core :: Graphics: WebRender, defect, P3)

Product:
Core
Component:
Graphics: WebRender
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
132 Branch
Tracking Flags:
Tracking Status
firefox-esr115 --- wontfix
firefox-esr128 --- wontfix
firefox130 --- wontfix
firefox131 --- wontfix
firefox132 --- fixed

People

(Reporter: jrmuizel, Assigned: ahale)

References

(Blocks 1 open bug)

Details

(Keywords: regression)

Right now we fallback to BasicLayerManager which isn't going to be a good time. Unfortunately, we're the only browser that supports SVG filters on HTML content.
Blocks: 1451112
Actually, Chrome and Safari support it as well.
This is a regression for Windows users because BasicLayerManager with Direct2D was at least hardware accelerated. With WebRender we disable Direct2D, so filters run on the CPU. It's also a regression for everyone because we don't have good invalidation support in the WebRender fallback code, so we always repaint the entire filter if anything inside it changes.
Summary: SVG filters on HTML content is bad time → SVG filters on HTML content is a bad time
Depends on: wr-svg-filter-perf
Blocks: wr-investigate
Blocks: 1468183
Depends on: 1480150
Depends on: 1480616
Depends on: 1480620
Blocks: 1494924
Priority: P1 → P3
Blocks: wr-svg-filter-perf
No longer depends on: wr-svg-filter-perf
Severity: normal → S3

If I am understanding the scope of this bug correctly (blob fallbacks when SVG filters are applied to HTML content), this is fixed by enabling gfx.webrender.svg-filter-effects in Bug 1906212 so I am closing this bug.

Assignee: nobody → ahale
Status: NEW → RESOLVED
Closed: 2 months ago
Depends on: 1906212
Resolution: --- → FIXED
status-firefox132: --- → fixed
You need to log in before you can comment on or make changes to this bug.