web_dev_style: check webui browser tests as well.

chrome/browser/ui/webui/downloads_ui_browsertest.js

Index: chrome/browser/ui/webui/downloads_ui_browsertest.js
diff --git a/chrome/browser/ui/webui/downloads_ui_browsertest.js b/chrome/browser/ui/webui/downloads_ui_browsertest.js
index f4e43c82f45f6cc652ee6333d070b229d5f39b76..d863df5093b6df7e9b121eee58bc87f5d96f4337 100644
--- a/chrome/browser/ui/webui/downloads_ui_browsertest.js
+++ b/chrome/browser/ui/webui/downloads_ui_browsertest.js
@@ -56,8 +56,10 @@ BaseDownloadsWebUITest.prototype = {
   /**
    * Creates a download object to be passed to the page, following the expected
    * backend format (see downloads_dom_handler.cc).
-   * @param {Number} A unique ID for the download.
-   * @param {Number} The time the download purportedly started.
+   * @param {number} A unique ID for the download.
+   * @param {number} The time the download purportedly started.
+   * @return {!Object} A fake download object.
+   * @private
    */
   createDownload_: function(id, timestamp) {
     var download = {};
@@ -78,7 +80,6 @@ BaseDownloadsWebUITest.prototype = {
     download.percent = 100;
     download.progress_status_text = 'done';
     download.received = 128;

[Tyler Breisacher (Chromium), 2014/04/28 23:13:26]

Out of curiosity, do you know if there's a good reason not to do this as an
object literal?

var download = {
  id: id,
  started: timestamp,
  ...
};

return download;

[Dan Beam, 2014/04/28 23:54:07]

Done.

-
     return download;
   },