diff options
| author | knn <knn@chromium.org> | 2015-12-15 23:04:00 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-12-16 07:04:54 +0000 |
| commit | 91d55c621307c578c233e3a07d896ce763abbae2 (patch) | |
| tree | 6fffde7d1b222b9275c70e63c6664ce48bf8698f /cc/BUILD.gn | |
| parent | 75c6e9cbbb47ad357a523f38eec2ad37b7ad8a35 (diff) | |
| download | chromium_src-91d55c621307c578c233e3a07d896ce763abbae2.zip chromium_src-91d55c621307c578c233e3a07d896ce763abbae2.tar.gz chromium_src-91d55c621307c578c233e3a07d896ce763abbae2.tar.bz2 | |
Always fire refresh tokens loaded on ChromeOS.
Unlike other platforms, ChromeOS does not trigger
ProfileOAuth2TokenService#LoadCredentials().
As of http://crrev.com/1380103004 we wait for RefreshTokensLoaded
notification before fetching the account info.
This cl ensures that notification is triggered correctly in the simplest
way. However this should ideally be handled within the
OAuth2TokenServiceDelegate or plumbed in a more explicit manner.
BUG=557906
NOTRY=true
Review URL: https://codereview.chromium.org/1523743003
Cr-Commit-Position: refs/heads/master@{#365491}
Diffstat (limited to 'cc/BUILD.gn')
0 files changed, 0 insertions, 0 deletions