Re: [w3ctag/design-reviews] Layout Instability Shifted Element Surfacing (#485)

On memory leaks: this actually came up on the PR and we made some changes as a result: `LayoutShiftAttribution` does not retain a DOM node after it is removed from a document.  The getter for the `node` attribute returns null in this case (via the "get an element" algorithm from the element timing spec).  So the attribution acts like a weak pointer, and still provides some information (new and previous visual rects) when `node` is null.

On privacy: we do not claim that fingerprinting applies to resource loading but not layout instability.  On the contrary, the intent is to disclose that layout instability _is affected by_ resource loading, and therefore shares the same theoretical fingerprinting opportunities.

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