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

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

Hi @torgo, thanks for taking a look at this.

> have there been any additional issues raised with element timing API regarding privacy or security that might inform the design of this extension?

Yes, there is the [`PaintTimingMixin`](https://github.com/w3c/paint-timing/issues/62) which was added to `PerformanceElementTiming ` last year and also  [`exposed`](https://github.com/w3c/largest-contentful-paint/issues/91) to `largest-contentful-paint`. This does expose some extra information around paint timing to both and its unsure at this time whether Container Timing would need these extra properties right now. There have been several learnings were recently applied to element timing around security, and container timing should be following all of them.

Secondly, Container Timing doesn't expose any new information on top of element timing, it just aggregates the same information for a container. All of the properties listed [here](https://github.com/bloomberg/container-timing?tab=readme-ov-file#performancecontainertiming) can be achieved by using element timing on all elements within the same area.

@mmocny and @jdapena should have more information if needed

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

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