chrome/browser/invalidation/invalidation_frontend.h - Issue 15517005: Remove references to Profile from browser_context_keyed_service.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: chrome/browser/invalidation/invalidation_frontend.h

Issue 15517005: Remove references to Profile from browser_context_keyed_service. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: rebase & style Created 7 years, 7 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

Index: chrome/browser/invalidation/invalidation_frontend.h

diff --git a/chrome/browser/invalidation/invalidation_frontend.h b/chrome/browser/invalidation/invalidation_frontend.h

index 8344e271e13d8cbaeddc4a3c05453a328ddc1db7..f8b61a5f54548114c9eeabac197ff937752bca83 100644

--- a/chrome/browser/invalidation/invalidation_frontend.h

+++ b/chrome/browser/invalidation/invalidation_frontend.h

@@ -45,7 +45,7 @@ namespace invalidation {

// It is an error to have registered handlers when an InvalidationFrontend is

// shut down; clients must ensure that they unregister themselves before then.

-// TODO(rlarocque): This class should extend ProfileKeyedService.

+// TODO(rlarocque): This class should extend BrowserContextKeyedService.

// NOTE(akalin): Invalidations that come in during browser shutdown may get

// dropped. This won't matter once we have an Acknowledge API, though: see