You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
What should happen if there is a descendant chain of elements all of which have content-visibility: hidden and all of which get a call to updateRendering?
It is likely that the update budget of the ancestors will cause us updates in descendants which will themselves be budgeted. Is this OK?
The text was updated successfully, but these errors were encountered:
Then we would update #a with background priority, which very likely means that we have some time budget within which we will do the work (this is an implementation detail that is tbd). If we exceed the budget, then we will yield and resume the next frame. However, since #b and #c and everything else is also background priority, it would presumably have their own time budgets. Or maybe they share #a's budget.
I'm just not sure exactly what is desired in this situation, but I admit that this is very likely an implementation detail that won't really matter for the use-cases we have.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What should happen if there is a descendant chain of elements all of which have content-visibility: hidden and all of which get a call to updateRendering?
It is likely that the update budget of the ancestors will cause us updates in descendants which will themselves be budgeted. Is this OK?
The text was updated successfully, but these errors were encountered: