Re: [w3ctag/design-reviews] Container Timing API (Issue #1034)

jdapena left a comment (w3ctag/design-reviews#1034)

About the Mixin:
- PerformanceContainerTiming entries should support the PaintTimingMixin. Internally we are already storing it, and that would be exposed the same way. Main thing is that we need to also provide a way to get the paint and presentation times for the first paint.
- Right now PerformanceContainerTiming.startTime is the last presentation time and lastPaintedElement is an element that was presented at that time. We need to decice if we want to have lastPresentedElement and lastPaintedElement. And we need to specify that startTime is the last presentation time explicitely.
- About firstRenderTime, maybe it should also be firstPresentationTime and firstPaintTime, and drop firstRenderTime. This way we will be able to get a complete view of presentation and painting.

Now, about the security/privacy: we need to incorporate the coarsening algorithm in the specification. I also need to review the native implementation (we are already using as input the coarsened numbers used for ElementTiming, so we should be already fine).

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1034#issuecomment-2777729181
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1034/2777729181@github.com>