diff options
| author | simonjam@chromium.org <simonjam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-12-16 01:15:57 +0000 |
|---|---|---|
| committer | simonjam@chromium.org <simonjam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-12-16 01:15:57 +0000 |
| commit | cb8a8742120db88ae594cc84cb2a046a7fa2cac4 (patch) | |
| tree | 0b7e59029a00bea062a19b72c152db3e585a9b54 /content/test | |
| parent | 4c4fa0299be73c03988278d486dd4d19bd14167e (diff) | |
| download | chromium_src-cb8a8742120db88ae594cc84cb2a046a7fa2cac4.zip chromium_src-cb8a8742120db88ae594cc84cb2a046a7fa2cac4.tar.gz chromium_src-cb8a8742120db88ae594cc84cb2a046a7fa2cac4.tar.bz2 | |
Use a monotonic clock (TimeTicks) to report network times to WebCore.
Navigation Timing (window.performance.timing) is now spec'd to use monotonically increasing time, so we need to follow suit. Most of this CL is just plumbing TimeTicks through. We already use TimeTicks to implement monotonicallyIncreasingTime() in WebCore.
On Windows, the clock doesn't tick uniformly between processes, so there is a layer in content that corrects for skew.
BUG=None
TEST=Adhoc (ran webtiming-* LayoutTests from Chrome) and content_unittests
Review URL: http://codereview.chromium.org/7602023
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@114736 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/test')
| -rw-r--r-- | content/test/render_view_fake_resources_test.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/test/render_view_fake_resources_test.cc b/content/test/render_view_fake_resources_test.cc index d8769c1..87d67a5 100644 --- a/content/test/render_view_fake_resources_test.cc +++ b/content/test/render_view_fake_resources_test.cc @@ -175,7 +175,7 @@ void RenderViewFakeResourcesTest::OnRequestResource( request_id, net::URLRequestStatus(), std::string(), - base::Time()))); + base::TimeTicks()))); } void RenderViewFakeResourcesTest::OnRenderViewReady() { |