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

[gagyibenedek]

Based on this example 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.

[tabatkins]

Because the property is of <image> type, it knows how to invalidate based on the loading state of images - when the image changes state, it'll automatically trigger a repaint, just like if you depended on a <length> property and changed the value.

Unsure about the possible bug, tho. @bfgeek?

[gagyibenedek]

I see, that makes sense. Thanks for the quick answer!
I think this information could be added to the CSSImageValue object description, since it's different from the way asynch loading is usually done (callbacks or promises), and this may surprise people. Should I open a PR? Or is this something that's better off in the MDN docs?