Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(289)

Issue 16228003: Use Date.now() rather than new Date().getTime(). (Closed)

Created:
7 years, 6 months ago by eroman
Modified:
7 years, 6 months ago
Reviewers:
mmenke1, mmenke
CC:
chromium-reviews, eroman, arv+watch_chromium.org, mmenke
Visibility:
Public.

Description

Use Date.now() rather than new Date().getTime(). Because Date.now() is faster. Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=203502

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+1 line, -1 line) Patch
M chrome/browser/resources/net_internals/time_util.js View 1 chunk +1 line, -1 line 0 comments Download

Messages

Total messages: 4 (0 generated)
eroman
This shouldn't really affect overall performance, but I figured I may as well update it. ...
7 years, 6 months ago (2013-05-31 19:55:07 UTC) #1
mmenke1
On 2013/05/31 19:55:07, eroman wrote: > This shouldn't really affect overall performance, but I figured ...
7 years, 6 months ago (2013-05-31 20:00:16 UTC) #2
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/eroman@chromium.org/16228003/1
7 years, 6 months ago (2013-05-31 20:07:04 UTC) #3
commit-bot: I haz the power
7 years, 6 months ago (2013-05-31 22:43:50 UTC) #4
Message was sent while issue was closed.
Change committed as 203502

Powered by Google App Engine
This is Rietveld 408576698