You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a long time the HTML Standard has marked fingerprinting vectors with a fingerprint image (along with appropriate alternative text). The idea is to generalize this in the Infra Standard to encompass all tracking vectors (see whatwg/infra#20 and whatwg/infra#115 in particular). I'd like to push this over the finish line, but thought I'd check in with the TAG to see if there's additional things to take into account here.
@dbaron and I took a look at this during our Tokyo F2F today.
It looks like there's a lot of useful discussion happening on whatwg/infra#115. In particular, several recent comments from @othermaciej identify a number of other kinds of tracking vectors that should be marked, including client-side storage mechanisms (notably absent from the text being moved here from HTML).
One other thought is that it's possible it's worth distinguishing between active and passive fingerprinting vectors. Perhaps that shouldn't be prominent, but I think it is a distinction worth thinking about, since I think there's consensus passive fingerprinting vectors are more serious than active ones (although probably not consensus on how much more serious).
We're really happy to see this move forward, and given that active discussion and improvement is happening in whatwg/infra#115, we're going to close this review for now. Please raise a new review request (& link to this one) if you'd like us to take another look when this firms up.
For a long time the HTML Standard has marked fingerprinting vectors with a fingerprint image (along with appropriate alternative text). The idea is to generalize this in the Infra Standard to encompass all tracking vectors (see whatwg/infra#20 and whatwg/infra#115 in particular). I'd like to push this over the finish line, but thought I'd check in with the TAG to see if there's additional things to take into account here.
cc @zcorpan
The text was updated successfully, but these errors were encountered: