Add more browsertests of chrome.identity.onSignInChanged event impl
This CL follows up on https://chromium-review.googlesource.com/593654 by adding another browsertest. This browsertest covers an aspect of the semantics that I had not realized before: - When the primary account signs in, a signin event fires not just for that account but also for all secondary accounts that have refresh tokens available. As described fully in the prior CL, these semantics are defined by examination of the AccountTracker implementation in preparation for refactoring away from using AccountTracker. This CL also updates the test with my new understanding that when a single state change causes multiple events to fire, the order in which these events fire is effectively undefined (to be precise, it's defined by internal implementation details of AccountTracker and ProfileOAuth2TokenService that are not part of those classes' public contracts). Bug: 729542 Change-Id: If10d3c25f0a5be015678dabae882d2eafc6f1212 Reviewed-on: https://chromium-review.googlesource.com/684835Reviewed-by:Ken Rockot <rockot@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#504711}
Showing
Please register or sign in to comment