Chris Harrelson

Are there any pseudo-elements we *do* want to support render-subtree on? The whole point is to avoid rendering the subtree, not the current (pseudo-)element.

I guess sites could abuse this feature in a user-hostile way. However, `user-select` already exists for the selection feature, and that one seems a stronger case for abuse from sites...

How about `renderPriority=`, where is one of the options in the [postTask](https://wicg.github.io/scheduling-apis/#enumdef-taskpriority) API, plus "auto" as default? e.g. `renderPriority=background` would mean do it when you can, `renderPriority=userVisible` would mean do...

> 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...

> There are things that attributes allow that are difficult in CSS. For instance, having UA change the attribute value is not easy/possible with CSS. But I think that's pretty...

Just remembered an important point: *if* content is on-screen and is not sync rendered, then there is a question about what we should display on-screen in the meantime, and how...

> 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...

I don't think Blink or other browsers are likely to be smart enough to know that an 'img' query selector doesn't require style.

Sorry I was being dumb somehow. `querySelectorAll` does not force style recalc. It only need to look at ids, classes, tag names and attributes. Therefore querySelectorAll and friends are just...

What they didn't want was to run out of memory. The use-case also explicitly said that it would be good to support find-in-page.