This results in different hashed device IDs on each session on embedders that don't have a specialized implementation of device ID salts such as WebView, Blimp and Content Shell. The new default helps prevent user fingerprinting on these embedders.
Since the new default logic is basically the same as for Chrome incognito mode, Chrome's implementation of salts has been updated to defer to the new default on incognito mode.
BUG=
315022
Committed:
https://crrev.com/4db1329e005388540eb07429ac97827ca9bc422b
Cr-Commit-Position: refs/heads/master@{#399883}