Chromium Code Reviews| Index: components/history/core/browser/history_types.h |
| diff --git a/components/history/core/browser/history_types.h b/components/history/core/browser/history_types.h |
| index 9189b068c5a15a32913cde65ed493b4261b6a0ce..c3e08af3d027e70a7870666a493a3c15cc2675e2 100644 |
| --- a/components/history/core/browser/history_types.h |
| +++ b/components/history/core/browser/history_types.h |
| @@ -526,6 +526,24 @@ struct FaviconBitmapIDSize { |
| gfx::Size pixel_size; |
| }; |
| +enum FaviconBitmapType { |
| + // The bitmap gets downloaded while visiting its page. Their life-time is |
| + // bound to the life-time of the corresponding visit in history. |
| + // - These bitmaps are re-downloaded when visiting the page again and the |
| + // last_updated timestamp is old enough. |
| + ON_VISIT, |
| + |
| + // The bitmap gets downloaded because it is demanded by some Chrome UI (while |
| + // not visiting its page). For this reason, their life-time cannot be bound to |
| + // the life-time of the corresponding visit in history. |
| + // - These bitmaps are evicted from the database based on the last time they |
| + // get requested. |
|
pkotwicz
2017/06/07 17:40:53
Nit: get -> were
jkrcal
2017/06/09 16:38:37
Done.
|
| + // - Furthermore, on-demand bitmaps are immediately marked as expired. Hence, |
| + // they are always replaced by ON_VISIT favicons whenever their page gets |
| + // visited. |
| + ON_DEMAND |
| +}; |
| + |
| // Defines a favicon bitmap stored in the history backend. |
| struct FaviconBitmap { |
| FaviconBitmap(); |