[css-houdini-drafts] [css-typed-om] How is state change in CSSURLImageValue handled?

gagyibenedek has just created a new issue for https://github.com/w3c/css-houdini-drafts:

== [css-typed-om] How is state change in CSSURLImageValue handled? ==
Based on [this example](https://drafts.css-houdini.org/css-paint-api/#example-2) the state change doesn't trigger any callback, it just has a new value at the next repaint. Is this correct? This seems strange, since the example from above needs some kind of continuous repaint (e.g. an infinite animation) for it to make sense, otherwise the actual image will never be shown, only the sad face.

Also, the code from above doesn't work on the latest Chrome, it stays in the 'unloaded' state indefinitely. Not sure if this is a Chrome bug or the code from the draft is outdated.

Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/741 using your GitHub account

Received on Thursday, 29 March 2018 14:16:31 UTC