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

Thank you for the explanation. Saving milliseconds to several seconds certainly sounds worthwhile to me.

> I agree that upgrading the renderpriority to something higher in the subtree is problematic, since it would violate the ancestor render priority setting and cause more work than necessary (as you mention with the ads injecting high priority content). I believe there is no such issues if we keep the priority at the minimum of ancestor and nested element (i.e. if one of them is background, then the content in the inner element is updated with background priority). We are also considering not updating nested renderpriority things at all (ie treat them as renderpriority=never), which would simplify reasoning about this and allow us to have improvements in the future.

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?

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