Clear the login webview when SAML flow is canceled

chrome/browser/resources/chromeos/login/screen_gaia_signin.js

Index: chrome/browser/resources/chromeos/login/screen_gaia_signin.js
diff --git a/chrome/browser/resources/chromeos/login/screen_gaia_signin.js b/chrome/browser/resources/chromeos/login/screen_gaia_signin.js
index 4abf255e226e5ad08acc32f6e7a75d63650396d0..0b307a319e78320cea599d122a89a876f94a6c89 100644
--- a/chrome/browser/resources/chromeos/login/screen_gaia_signin.js
+++ b/chrome/browser/resources/chromeos/login/screen_gaia_signin.js
@@ -593,10 +593,12 @@ login.createScreen('GaiaSigninScreen', 'gaia-signin', function() {
           break;
 
         case ScreenMode.OFFLINE:
+          this.gaiaAuthHost_.resetStates();

[emaxx, 2016/05/23 15:00:49]

This (plus the new line 601) resolves the issue that the SAML webview was still
working in the background, when the network becomes disconnected.

The network disconnection results in loading the first screen, which is
performed by the GaiaSigninScreen.loadAuthExtension method call. With this
patch, this results in calling resetStates() on all code paths (note: when
this.screenMode_==ScreenMode.DEFAULT, GaiaSigninScreen.loadGaiaAuthHost_ will
call resetStates itself).

           this.loadOffline(params);
           break;
 
         case ScreenMode.SAML_INTERSTITIAL:
+          this.gaiaAuthHost_.resetStates();
           $('saml-interstitial').domain = data.enterpriseDomain;
           if (this.loading)
             this.loading = false;
@@ -923,7 +925,7 @@ login.createScreen('GaiaSigninScreen', 'gaia-signin', function() {
      */
     reset: function(takeFocus, forceOnline) {
       // Reload and show the sign-in UI if needed.
-      this.gaiaAuthHost_.resetStates_();
+      this.gaiaAuthHost_.resetStates();
       if (takeFocus) {
         if (!forceOnline && this.isOffline()) {
           // Show 'Cancel' button to allow user to return to the main screen