From 30a74553b2e067ebcb63f03f86226d7fd2730f94 Mon Sep 17 00:00:00 2001 From: "dubroy@chromium.org" Date: Wed, 13 Mar 2013 13:36:14 +0000 Subject: Push check for Time::is_max() from BrowsingDataRemover to HistoryBackend. No functionality change -- this just allows BrowsingDataRemover to call HistoryBackend::ExpireHistoryBetween with a null |end_time|, and still have it properly detected as the "remove all history" case. BUG=145680 Review URL: https://chromiumcodereview.appspot.com/12766003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@187858 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/browser/history/history_backend.cc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'chrome/browser/history') diff --git a/chrome/browser/history/history_backend.cc b/chrome/browser/history/history_backend.cc index 95980cf..26a0d9d 100644 --- a/chrome/browser/history/history_backend.cc +++ b/chrome/browser/history/history_backend.cc @@ -2713,7 +2713,8 @@ void HistoryBackend::ExpireHistoryBetween( Time begin_time, Time end_time) { if (db_.get()) { - if (begin_time.is_null() && end_time.is_null() && restrict_urls.empty()) { + if (begin_time.is_null() && (end_time.is_null() || end_time.is_max()) && + restrict_urls.empty()) { // Special case deleting all history so it can be faster and to reduce the // possibility of an information leak. DeleteAllHistory(); -- cgit v1.1