MD History/Downloads: convert .bind(this) and function property values to use =>

chrome/browser/resources/md_history/synced_device_card.js

 // Copyright 2016 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.
 
 Polymer({
   is: 'history-synced-device-card',
 
   properties: {
     // Name of the synced device.
     device: String,
 
     // When the device information was last updated.
     lastUpdateTime: String,
 
     /**
      * The list of tabs open for this device.
      * @type {!Array<!ForeignSessionTab>}
      */
     tabs: {
       type: Array,
-      value: function() { return []; },
+      value: () => [],

[dpapad, 2016/12/21 23:49:53]

Can we use arrow only when:
 1) Used inside a member function.
 2) we previously we used bind()
 
for now? I am leaning towards considering non-bound functions more readable with
the old syntax.

[michaelpg, 2016/12/22 07:35:19]

why?
why?? (why limit it to that?)

[Dan Beam, 2016/12/22 18:33:17]

well, I obviously agreed with ... myself when I made this change, but my
understanding of what dpapad@ is saying is that: => shines most when we're able
to drop .bind(this).  nobody's arguing against that, afaik.

       observer: 'updateIcons_'
     },
 
     /**
      * The indexes where a window separator should be shown. The use of a
      * separate array here is necessary for window separators to appear
      * correctly in search. See http://crrev.com/2022003002 for more details.
      * @type {!Array<number>}
      */
     separatorIndexes: Array,
@@ skipping 123 matching lines @@
     });
     e.stopPropagation();  // Prevent iron-collapse.
   },
 
   onLinkRightClick_: function() {
     md_history.BrowserService.getInstance().recordHistogram(
         SYNCED_TABS_HISTOGRAM_NAME, SyncedTabsHistogram.LINK_RIGHT_CLICKED,
         SyncedTabsHistogram.LIMIT);
   },
 });