The canvas APIs allow websites to draw shapes and forms on a canvas and read back the rendered image. However, the browser's rendering process leaks details about the GPU's properties. The goal of adding noise to canvas readbacks is to prevent scripts from easily obtaining identifying information that can be used to re-identify a browser across contexts. The noise that is added to the pixels is deterministic for a given canvas, and changes based on the site of the embedding document. With this feature noise would only be added to canvas readbacks for users in Incognito mode.
The specific way in which shapes and forms are rendered on the GPU expose information about the characteristics of that GPU. By adding noise to the pixel values upon readback, easily obtaining identifying information that can be used to re-identify a browser across contexts is no longer feasible.
None
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
No milestones specified
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/67d8ad03.2b0a0220.1cd73d.0b3e.GAE%40google.com.