diff options
| author | georgesak <georgesak@chromium.org> | 2015-05-14 20:01:50 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-05-15 03:02:07 +0000 |
| commit | 041ef9c96d9a5b6f206a24385b0e6e4b3dbf9f20 (patch) | |
| tree | 8550fce8183df4b1132d3b6d4859f3dcdc32dba7 /content/browser/BUILD.gn | |
| parent | 4bae6ed4c1a8a249a83414b8f8e9fb00e6cc66bb (diff) | |
| download | chromium_src-041ef9c96d9a5b6f206a24385b0e6e4b3dbf9f20.zip chromium_src-041ef9c96d9a5b6f206a24385b0e6e4b3dbf9f20.tar.gz chromium_src-041ef9c96d9a5b6f206a24385b0e6e4b3dbf9f20.tar.bz2 | |
Change WebContents::last_active_time_ to Time instead of Timeticks.
For context, last_active_time_ is going to be used by session restore to order the loading of background tabs using MRU. In order for this to be robust, last_active_time_ must be saved and restore between sessions. Timeticks cannot be reliably restored as it's dependent on the current OS session. MRU code for session restore is being implemented in https://codereview.chromium.org/1131373003
Notes:
- In dev tools, replaced "activity" with "active" for consistency
- In OomPriorityManagerTest.Comparator, initialized last_active_time for all tabs, as this is necessary with Time (a default TimeTicks can go back in time, not the case with Time).
BUG=472772
Review URL: https://codereview.chromium.org/1140083004
Cr-Commit-Position: refs/heads/master@{#330029}
Diffstat (limited to 'content/browser/BUILD.gn')
0 files changed, 0 insertions, 0 deletions