Dan: so one feedback is that they jump right into talking about JS profiling without talking about the developer or user need.... A sentence such as "this is in service of making web apps more reliable" etc.. might be helpful.

Yves: can it be used to detect on the mobile if you are on battery saver mode... If you're profiling and you realise youre running slower than usual...

Dan: Fingerprinting issue?

Lea: seems like a stretch

Ken: Agree

Dan: Worth asking the question - have they considered how this could be used by fingerprinters and mitigation strategy...?

Ken: this is the extension of the existing profile API using markers... adding a marker to what's going on... so more detailed information... The developer marks what they're interested in .. they get a timestamp ..

Ken: not just scripting... also css, etc... system might work well on your super fast machine .. but might be very expensive layout on older devices...

Yves: if it's just markers then...

Ken: The sspec is called js self profiling but profiling things that are not javascript...

Lea: given that these markers are predefined the scope seems limited. At first I thought it was general purpose but doesn't seem to be the case...

Ken: you give the profiling a set of markers...

Dan: any cross-origin info?

Ken: no it's only for that tab - only for that origin.

Dan: seems like they need to be explain the mitigation a but more... leaves comment.

Ken: fine with the API... No difference.

Dan: it does enlarge of the scope ....

Ken: Definitely. Maybe it would be nice if ... it's good gor UAs ...

Dan: ken left a comment... no response so far...

assigns Sangwhan

Dan: this is about JavaScript performance. Explainer does not define the user need ...

Sangwhan: provenance - it's from a non-browser org... so this makes sense. Presumably they want to capture traces & profiles at the end user level instead of having to capture with devtools?

Dan: leaves comment

Max: We need to wait for a response from requester

Sangwhan: did we do any technical analysis?

Dan: my comments were all about process

Sangwhan: I'll look at it

Max: waiting for the authors to respond...

Dan: comments recently..

Sangwhan: will re-ask my question..

Dan: they didn't respond about multistakeholder

Dan: Sangwhan left a comment. Looks like not much update since then.

Max: We had a discussion, the authors didn't respond yet

Dan: Plenary? Wait to next week for Sangwhan

Amy: looks like waiting for response

Sangwhan: I think this is pending because it's paused at the moment. We can probably close this. [will comment]

closed