Hi everyone!
Join us <https://meet.google.com/agz-fbji-spp> this week to talk about
Long Tasks and requestIdleCallback.
On the agenda
<https://docs.google.com/document/d/10dz_7QM5XCNsGeI63R864lF9gFqlqQD37B4q8Q46LMM/edit?pli=1#heading=h.osvewfb7hvdz>,
we have:
*
Long Tasks
o Top-level browsing context scoping
<https://github.com/w3c/longtasks/issues/75>
o Event loop timing reporting seems to ignore reentrancy
<https://github.com/w3c/longtasks/issues/76>
o Combination of paint timing and long tasks can expose precise
paint timing <https://github.com/w3c/longtasks/issues/80>
* requestIdleCallback
o timeRemaining() step 4 should define what it means to have a
"time-critical task pending
<https://github.com/w3c/requestidlecallback/issues/87>
o 6.2. invoke idle callbacks algorithm step 1 should be defined in
terms of task sources having tasks enqueued
<https://github.com/w3c/requestidlecallback/issues/86>
o The order of idle callbacks across windows is inconsistent
between spec & UAs
<https://github.com/w3c/requestidlecallback/issues/82>
If you have any additional items you'd like to discuss, please add to
the agenda
<https://docs.google.com/document/d/10dz_7QM5XCNsGeI63R864lF9gFqlqQD37B4q8Q46LMM/edit?pli=1#heading=h.osvewfb7hvdz>.
If we get though those, we may venture into ServerTiming issues.
The meeting will be recorded and published online afterwards.
See you soon!
- Nic Jansma
@nicj
Received on Monday, 6 April 2020 12:39:54 UTC