Profile::IsNewProfile() sometimes returns false for the default profile |
||||
Issue descriptionBecause IsNewProfile() is implemented by checking if the preferences file was created on the current Chrome execution, it misses the case where a master_preferences file exists, and is dumped into the default profile on creation. When the profile loads for the first time, the file already exists and is thus not considered a new one, even though it should. The easiest fix is to change IsNewProfile() to also check for first_run::IsChromeFirstRun(), because every profile on first run is new.
,
Jul 2
--Chrome Identity automated triaging-- This bug is Available and has gone one year without any activity. If another month passes without any activity, this bug will be closed out. Please provide an update with the latest status for this bug. 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
,
Jul 2
I imagine this is still valid, so pinging for Patrick to keep it alive. Feel free to re-assign to someone else if you're no longer the right owner, Patrick.
,
Aug 2
,
Sep 3
--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 sheriffbot@chromium.org
, Jul 3 2017