- From: François REMY <francois.remy.dev@outlook.com>
- Date: Sat, 27 Jun 2015 00:09:37 +0200
- To: "'Ian Kilpatrick'" <ikilpatrick@chromium.org>, <public-houdini@w3.org>
> Greg, Rossen, Shane, Tab & I sat down over VC today > and did a read-through of any issues initially that might > arise. > > Please have a read and let us know of any feedback on > the API design and potential issues. > > http://dev.w3.org/houdini/css-paint-api/ LGTM except I don't see any issue mentioning that resources like images or videos might be required to draw the painting. How can the handler communicate that the rendering isn't done yet and invalidates himself asap (once the image loaded, for instance), or aren't we going to support this at all? I guess animated paintings are supported by marking the painting dependent of a "--painting-time" custom property which can be continuously updated from 0 to 100% by an animation. That does not require a specific api, allowing to keep things simple by default. I'm slightly in favor of reusing last frame in case a painting doesn't finish on time, so that at the very least a painting that misses one frame doesn't flash empty. If the target geometry has changed, then the image is just used as-is and transparent sections may appear where there was previously no rendering. What do you think?
Received on Friday, 26 June 2015 22:10:16 UTC