Respect opt_scopes in getNewToken.

remoting/webapp/app_remoting/js/app_connected_view.js

 // Copyright 2015 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 /**
  * @fileoverview
  * Implements a basic UX control for a connected app remoting session.
  */
 
 /** @suppress {duplicate} */
@@ skipping 220 matching lines @@
  * @param {function(string, string)} sendExtensionMessage
  * @private
  */
 remoting.AppConnectedView.prototype.sendGoogleDriveAccessToken_ =
     function(sendExtensionMessage) {
   var googleDriveScopes = [
     'https://docs.google.com/feeds/',
     'https://www.googleapis.com/auth/drive'
   ];
   remoting.identity.getNewToken(googleDriveScopes).then(
-    function(/** string */ token){
+    function(/** string */ token) {
+      base.debug.assert(token !== previousToken_);
+      previousToken_ = token;
       sendExtensionMessage('accessToken', token);
   }).catch(remoting.Error.handler(function(/** remoting.Error */ error) {
     console.log('Failed to refresh access token: ' + error.toString());
   }));
 };
 
+// The access token last received from getNewToken. Saved to ensure that we
+// get a fresh token each time.
+var previousToken_ = '';

[kelvinp, 2015/05/11 17:17:33]

This can be moved inside the scope of sendGoogleDriveAccessToken_

[Jamie, 2015/05/11 17:23:08]

I think it's clearer as a global. Javascript scoping and lifetime rules for vars
are a bit unusual to someone not well versed in the language, and since we're in
a IIFE, there's little benefit to scoping it more tightly than this.

+
 })();