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

Issue 10447110: WebKit will start using NaN to indicate null/invalid time (Closed)

Created:
8 years, 6 months ago by kinuko
Modified:
8 years, 6 months ago
CC:
chromium-reviews, erikwright (departed), darin-cc_chromium.org, brettw-cc_chromium.org
Visibility:
Public.

Description

WebKit will start using NaN for null/invalid modificationTime Per discussion on webkit bugzilla WebKit will start using NaN for null/invalidmodificationTime (instead of 0.0, our conventional null time value) https://bugs.webkit.org/show_bug.cgi?id=87709#c10 https://bugs.webkit.org/show_bug.cgi?id=87826 BUG=none TEST=existing tests should pass Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=140710

Patch Set 1 : #

Unified diffs Side-by-side diffs Delta from patch set Stats (+13 lines, -1 line) Patch
M base/time.cc View 3 chunks +13 lines, -1 line 0 comments Download

Messages

Total messages: 2 (0 generated)
kinuko
I can instead only changing glue code between WebKit/chromium boundary but it sounds very error ...
8 years, 6 months ago (2012-06-05 12:11:05 UTC) #1
brettw
8 years, 6 months ago (2012-06-05 19:41:24 UTC) #2
lgtm

Powered by Google App Engine
This is Rietveld 408576698