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

How does this work with nesting? E.g. if I have an ancestor with `renderpriority="background"` and a descendant with `renderpriority="user-blocking"`, doesn't that effectively cancel the ancestor's `renderpriority`, since the ancestor would need to be rendered to render the descendant?

Wouldn't that also enable advertisers from just injecting HTML with `renderpriority="user-blocking"` to hog resources for their ads?

I would also have liked a discussion on what kind of performance gain would this enable, for a sufficiently complex DOM (e.g. the HTML spec). Are we increasing the complexity of the web platform to save some nanoseconds or is it a more significant gain?

> An example use case is optimizing the speed of single-page-application navigations. If the application can predict a likely user action, then it can prerender the next view offscreen via content-visibility: hidden plus renderpriority. This will make the single-page application navigations faster for the user.

How would an author use `renderpriority` to enable this use case? What value would they use? Are they supposed to change the value before navigation?

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