[cssom] "Specifications that define static functions on ..."

[zcorpan]

https://drafts.csswg.org/cssom/#example-fc08f03e

Specifications that define static functions on the CSS interface and want to store some state should store the state on the current global object’s associated Document.

In w3c/css-houdini-drafts#410 (comment) @domenic says

I agree things are a bit confusing here. I probably was the one who suggested "should store the state on the current global object’s associated Document." But I am not sure why that is better than just "the current global object". All the "associated Document" bit does is make things confusing when document.open() gets involved. So maybe if we simplified it to just "the current global object" as the rule for all static things (and all namespace things), it would be better.

The text was added in e9edde3 for #180.

The relevant method under discussion is registerProperty(), w3c/css-houdini-drafts#216 . It seems better to me to have that state go away with document.open(), just like any stylesheets go away. But if paintWorklet should be on the global instead, I suppose we need to nuance the advice or drop it...