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

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

> Hi all. We are looking at this in our TAG breakout. Two quick questions (and then likely more to follow):
> 
> 1. Do you think this adds to the fingerprinting surface area for a user (or UA context)?

As this can be polyfilled on top of Element Timing, it does not really add any new fingerprinting surface. Same considerations should be made for intersection rect and timers. The native implementations should be using coarsened timers as in ElementTiming.

> 3. How do you expect the coarsening algorithm to work here? Can you spell that out for us?

I think the Element Timing API security and privacy section applies pretty well here: https://w3c.github.io/element-timing/#sec-security

We will need to add a reference to it or repeat most of the Element Timing wording for the Container Timing render time details.

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

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