Contact emails
[email protected]

Explainer
https://github.com/w3c/event-timing/pull/160


Specification
https://github.com/w3c/event-timing/pull/160


Summary
The Event Timing API (part of the Performance Timeline) is used to measure 
long-running user interactions. Each entry reports the event type, timeStamp, 
processing times, and total duration to next paint. Currently, each entry 
already reports the EventTarget (node), which is very important to actually 
find a reproduction use case from field data, in order to fix latency issues. 
This new feature additionally exposes a String representation of the 
EventTarget via a new `targetSelector` attribute of Event Timing API. 
Motivation: because observing Event Timing is asynchronous, and because the 
`target` value is a weak reference, and because interactions with a page often 
modify the page (eg clicking a cookie consent prompt, or a button to dismiss a 
modal dialog), it is fairly common that the `target` Node might have already 
disconnected from the DOM and become reporting as `null`. By capturing a light 
weight representation of the node (as a querySelector formatted string) we can 
keep a strong reference for reporting purposes.


Blink component
Blink>PerformanceAPIs


Web Feature ID
event-timing


Goals for experimentation
None


Risks




Interoperability and Compatibility
No information provided

Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:


WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it 
has potentially high risk for Android WebView-based applications?
No information provided



Debuggability
No information provided


Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, 
ChromeOS, Android, and Android WebView)?
No


Is this feature fully tested by web-platform-tests?
No



Flag name on about://flags
No information provided


Finch feature name
No information provided


Non-finch justification
No information provided


Requires code in //chrome?
False


Tracking bug
https://crbug.com/40887145


Estimated milestones

No milestones specified



Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5143499213242368


Links to previous Intent discussions
Intent to Prototype: 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEeF2TfzH7wEOaLmr_b6DPCqhQxiXTThDGrMKGoRA-JnNudjPw%40mail.gmail.com



This intent message was generated by Chrome Platform Status.

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69c18f43.050a0220.2e80d7.03df.GAE%40google.com.

Reply via email to