50 ms·
I suspect that as long as getComputedStyle() exists, there will be ways for it to leak identifying information. Browsers already break getComputedStyle for some
by ubernostrum 10y ago
I suspect that as long as getComputedStyle() exists, there will be ways for it to leak identifying information. Browsers already break getComputedStyle for some things (i.e., to close the history leak of being able to query whether the "visited" styling is applied to a link), but it may end up that this API just has to disappear completely.
- majewsky 10y agoTrue. I always feel like we are at the point where we shouldn't think about which APIs to add to our browsers, but about which APIs to remove. Browser vendors frequently deprecate SSL versions and ciphers, and in the same vein, we should sacrifice at least some backwards compatibility for more privacy.