Re: [w3ctag/design-reviews] renderPriority element attribute (#676)

> Given that the default renderpriority is `user-visible`, wouldn't that effectively render `user-blocking` impossible to use, unless you're willing to set it on the root, defeating its purpose?

Hmm, the default value is `auto` which allows the user-agent to select "whatever is appropriate". You're right that we need to be careful not to set a lower default (I'll update the explainer to call this out). Currently though, we're only proposing that this attribute has an effect only if rendering of the contents of that element would be skipped by the user-agent. From the explainer,
```
If the User Agent does not optimize rendering of elements, by skipping work, then the attribute has no effect.
```
The question is, of course, if it has no effect on the element, does it still affect the nested `renderattribute` settings. I don't think it should, but that's not (yet) clear in the explainer.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/676#issuecomment-942536515