Nicolás Peña Moreno

Would it be possible to implement this with your task tracking idea @yoavweiss ? How standardizable is that

So a task can be paused for an arbitrary amount of time and then that same task would be resumed? It's true that this would probably introduce a longtask. Chrome's...

But if I'm understanding this correctly, these nested event loops are limited in what they can do, and in particular they cannot process user input right? I'm not sure where...

So if the task is stopped and the browser is now able to handle new high priority tasks (such as input), that would constitute the end of the current task....

So the 'spin the event loop' could be expanded to change the timing variables when stopped and when resumed so the task is broken into two separately timed parts. But...

Discussed at the call, people seemed to agree that an sync xhr or an alert() blocking other work should be punished, so it's fine that it would produce a longtask....

Yea, we know current attribution needs to be improved, although not sure when we'll get to work on this. How would the callstack to work when there are multiple top-level...

We're currently punting this, waiting to see if the Sampling Profiler API ships. If it does, we could benefit from it to expose some useful information about tasks that take...

It is a proposed API, although I'm not the one working on it: https://github.com/WICG/js-self-profiling

To answer the question, it is intentional because of the performance overhead of monitoring longtasks (not sure if this is still applicable on Chrome at this point...). Thus, we do...