Re: [w3ctag/design-reviews] Other Spec Review: named-feature() function for CSS @supports (Issue #1186)

dbaron left a comment (w3ctag/design-reviews#1186)

One note about fingerprinting:  I think the risk of additional entropy is pretty low since I think all or nearly all of these features are already detectable in Javascript.  The three features that have been considered to be named features so far certainly all are.  And even if there's one that isn't, other features that ship in the same browser version likely will be detectable in javascript.  I don't think there's any reasonable hope for obscuring browser engine version (at least major version, with a possible exception for security patches) from fingerprinting entropy.  The best solution to reducing the real effects of that is ensuring quick and broad uptake of browser engine updates.

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

Message ID: <w3ctag/design-reviews/issues/1186/4557950886@github.com>