Dan: working on React.. CDT integration was great
… there is no way for a library to tell if user is recording or not, we're afraid of wasting memory
… we're calling clearmarks/measures all the time, but it means we can't harvest it later
… our main target is CDT
… i.e. in dev mode
a) sounds like there is a need for API in devtools for in "record mode"
b) you should log some data to performance timeline.. perhaps with lower fidelity
Nic: we monitor React today, we look at routechange events
Dan: we expose UT for every component in dev mode
Enforce payload limits via Fetch API: https://github.com/w3c/beacon/pull/39
Q: is this L2 or L3 feature?
we'll revisit next time.
Set `name` to document address: https://github.com/w3c/navigation-timing/pull/61
shipping in M57 in Chrome, stable ~mid march
we'll pause landing it until we have confidence in it
next: charter update
Todd: we need/want charter update from MSFT end
… I'll review and merge, first pass looks good
we'll followup with plh@ on next steps
xiaoqian: we probably need a test for prerender.
AI: let's start a new issue on the repo
we'll wait for PR until we resolve ^
Todd: there are tests in the WPT tree that require user input
L2 CR for UT: https://github.com/w3c/user-timing/issues/19
Todd: I'll try to get the updated tests.
We'll try to triage UT2 issues before next call
next call: March 22nd
Unknown options in environment variable SCRIBEOPTIONS:
No scribenick or scribe found. Guessed: igrigorik
Maybe present: AI, Dan, Nic, Q, Todd, next, timeline, xiaoqian