MediaDeviceIDSalt should not be part of the BrowserContext/Profile |
|||||||
Issue descriptionAs of when https://codereview.chromium.org/2820163002/ lands, MediaDeviceIDSalt will be part of the content::BrowserContext API. Instead, it should use a BrowserContextKeyedService (Or some other mechanism) to associate it with the BrowserContext.
,
Apr 20 2017
Oops, sorry, assigned to wrong person!
,
May 22 2017
--Chrome Identity automated triaging-- This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 14 2017
,
Sep 14 2017
,
Oct 16 2017
As part of the rewrite, consider using base::UnguessableToken to implement the actual salt.
,
Jul 18
,
Aug 20
--Chrome Identity automated triaging-- This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by guidou@chromium.org
, Apr 20 2017