Issue 164137 in chromium: Hardware acceleration support for CSS and SVG filters

[chro...@googlecode.com]

Status: Assigned
Owner: pe...@chromium.org
CC: senorbla...@chromium.org
Labels: OWP-Type-ChangeBehavior OWP-DesignReview-No
OWP-Standards-Compatibility OWP-Format-Unprefixed OWP-LaunchBug-Needed
OWP-Documentation-Needed Type-Launch-OWP OWP-TargetChannel-Stable Mstone-27
Pri-2

New issue 164137 by pe...@chromium.org: Hardware acceleration support for
CSS and SVG filters
http://code.google.com/p/chromium/issues/detail?id=164137

*High-level description of the change (1-2 sentences):*
Support for hardware acceleration in rendering CSS and SVG filters. This
will significantly improve performance of applying filters to elements, and
will presumably work better with compositing as well.

*Listing of additions/modifications/changes to API surface (bullet
points):*
No API changes.

---------
Additional context (fill in as much as you can, or link to a prior API
launch bug with the context):
*Link to relevant webkit or crbug:*
Issue 61527 - "GPU-accelerated SVG"

Standards / other vendor support isn't relevant here, as this is a
technical improvement of our existing implementation.

[chro...@googlecode.com]

Updates:
Cc: schen...@chromium.org

Comment #1 on issue 164137 by pe...@chromium.org: Hardware acceleration

support for CSS and SVG filters
http://code.google.com/p/chromium/issues/detail?id=164137

Stephen (either :-)), comment 24 on Issue 61527 mentions that work is still
under way. Is there a set milestone to finish implementation of the HW
accelerated filters, and what's the best way to keep track of progress?

[chro...@googlecode.com]

Comment #2 on issue 164137 by senorbla...@chromium.org: Hardware

acceleration support for CSS and SVG filters
http://code.google.com/p/chromium/issues/detail?id=164137

There are actually a number of different aspects to this:

1) accelerating (traditional) SVG filters
2) accelerating shorthand CSS filters (blur, sepia, saturate, etc)
3) SVG filters on HTML elements (the "reference" filter in the CSS filter
effects spec)
4) accelerating SVG filters on HTML elements (#3, but on composited layers)

#2 is shipping as of M19: filters on composited layers are accelerated, as
are animated filters (they trigger the compositor while animated, then drop
back to software). #3 is shipping as of M21. The infrastructure for #4 is
done in M25 canary, as are about 6 of the filters. I had hoped to get the
rest done for M25 (all but 2 have skia implementations; most just need to
be enabled in WebKit), but that has been derailed by other priorities.

I have a pair of docs I'm using to keep track of progress which I'll share
with you.

The work for #4 will easily allow #1 to be done, but I doubt we will do
that until accelerated drawing is enabled generally (essentially issue
61527).

[chro...@googlecode.com]

Updates:
Labels: Cr-Blink-CSS-Filters

Comment #6 on issue 164137 by senorbla...@chromium.org: Hardware

acceleration support for CSS and SVG filters
http://code.google.com/p/chromium/issues/detail?id=164137

(No comment was entered for this change.)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings