history: remove unused variable.

chrome/browser/resources/history/history.js

Index: chrome/browser/resources/history/history.js
diff --git a/chrome/browser/resources/history/history.js b/chrome/browser/resources/history/history.js
index 50b79464f73a7ca17cb4e608578e2eab3166b1de..6a987dc3b81007bfa7c73109f1764e63f117880c 100644
--- a/chrome/browser/resources/history/history.js
+++ b/chrome/browser/resources/history/history.js
@@ -1798,7 +1798,6 @@ PageState.prototype.getHashData = function() {
   var result = {
     q: '',
     page: 0,
-    grouped: false,
     range: 0,
     offset: 0
   };
@@ -1809,9 +1808,8 @@ PageState.prototype.getHashData = function() {
   var hashSplit = window.location.hash.substr(1).split('&');
   for (var i = 0; i < hashSplit.length; i++) {
     var pair = hashSplit[i].split('=');
-    if (pair.length > 1) {
+    if (pair.length > 1)
       result[pair[0]] = decodeURIComponent(pair[1].replace(/\+/g, ' '));
-    }
   }
 
   return result;
@@ -1879,7 +1877,6 @@ function load() {
 
   // Create default view.
   var hashData = pageState.getHashData();
-  var grouped = (hashData.grouped == 'true') || historyModel.getGroupByDomain();

[Evan Stade, 2014/08/04 21:50:05]

I guess that it would make more sense to either use this, i.e. 

  historyView.setGroupedByDomain(grouped)

or remove the grouping by domain completely.

+sergiu who seems to own this feature

[Sergiu, 2014/09/09 08:59:24]

Removing this should be fine. We actually infer the "grouped" state from the
range (you can see groupedByDomain being set in setPageState here:
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/browser/res...).

[Dan Beam, 2014/09/10 23:20:46]

Removed the local var, left this.groupByDomain_ as it's still used.

   var page = parseInt(hashData.page, 10) || historyView.getPage();
   var range = parseInt(hashData.range, 10) || historyView.getRangeInDays();
   var offset = parseInt(hashData.offset, 10) || historyView.getOffset();