Re: [mediacapture-main] fixed, per origin, device ID creates tracking risk (#607)

> I'm saying the opposite: if double keying of both cookies and localStorage isn't standardized—which I doubt will ever happen.

Safari is implementing partitioning for localStorage, IDB, service workers without too much breakage. Cookies is indeed another story.

>  If third-party cookies are blocked, then block persisting third-party deviceIds.

It seems like you are advocating for some form of partitioning.
You might end up having different deviceIds for the same resource, be it loaded as a main frame (persistent ids) or loaded as a third-party iframe (non persistent ids).

GitHub Notification of comment by youennf
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 24 July 2019 23:07:22 UTC