Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

updateRendering: What happens with multiple subtree calls? #198

Open
vmpstr opened this issue Sep 8, 2021 · 2 comments
Open

updateRendering: What happens with multiple subtree calls? #198

vmpstr opened this issue Sep 8, 2021 · 2 comments

Comments

@vmpstr
Copy link
Collaborator

vmpstr commented Sep 8, 2021

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?

@noahlemen
Copy link

Could you clarify what you mean by "update budget" here? I'm having some trouble wrapping my head around this scenario.

@vmpstr
Copy link
Collaborator Author

vmpstr commented Sep 15, 2021

I mean if we have something like

<div id=a renderPriority=background>
 ...
 <div id=b renderPriority=background>
  ...
  <div id=c renderPriority=background>
  ...

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants