vmpstr
vmpstr
That sounds good. Would `auto` be equivalent to `userBlocking` in this case? IOW, I assume userBlocking means the same thing as do it as if you're always updating the rendering
That's an interesting question. Here's how I think about it: ``` /* some other content */ ``` in the above, renderPriority has no effect and contents of `#target` will not...
I think renderpriority is sticking as a name (#205 suggested different case, per guidelines). So I'm going to close this
I've spent some time thinking about this and I keep coming back to the question of what is the difference between attributes and properties. So here comes my philosophical rant...
I think the point that "if this is a CSS property, then it can still be controlled by an attribute due to the power of selectors" is very good. This...
This is a good point. This is the main reason why I wouldn't want to tackle this as part of the renderPriority work. We should pursue this work as a...
Sorry for the (very very) late reply, but this method's name is confusing since it provides different utility. You can read some context here: https://github.com/w3c/csswg-drafts/issues/7317
rendersubtree="invisible will-measure-layout"? or updateRendering({ why: "want layout" })?
This might be useful as a dictionary to updateRendering which would ask for specific work
I wonder if for `content-visibility: auto` if we should have evict memory objects if we're far enough off-screen