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

Thank you for your feedback and questions!

> On attribute vs CSS property we definitely think this is more suitable as a CSS property. This way it is easier to use it for creating defaults, including in Web components, and also given that it interacts with other CSS properties.

That makes sense, thanks.

> We are still not sure about certain details of the proposed algorithm, including my question from above about nesting higher priority elements inside lower priority elements.

The intent is to have this property be treated as a maximum rendering priority for itself and its descendants. This would mean that higher priority descendants would still be limited by the lower priority ancestors. In other words, a parent with a baackground priority will cause all of its children to update with at most a background priority, even if one of its children is a user-blocking priority. 

> We would like to see some examples of actually using the feature to target the user needs you are targeting. Are all these values necessary to address these use cases?

* user-blocking - this is currently the behavior for most (all?) visible content: updates always happen synchronously even if that blocks other work
* user-visible - this priority isn't really required (the priorities were largely inspired by the [task scheduling api](https://wicg.github.io/scheduling-apis/#enumdef-taskpriority))
* background - this is the most interesting priority to us, since that would allow developers to update `content-visibility: hidden` subtrees without blocking other important work.
* never - this is currently the behavior for `content-visibility: hidden` subtrees, since the rendering in those subtrees is not updated.
* auto - this seems like a nice default for the UA to select another priority. For example, UA can select "user-blocking" for visible content and "never" for content with `content-visibility: hidden` subtrees.

I don't have any working examples since we don't have a working prototype of this feature, but I can work to construct hypothetical examples where this would be useful.

Thanks again!



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

Message ID: <w3ctag/design-reviews/issues/676/1168877953@github.com>