chrome/browser/extensions/api/messaging/message_service.h - Issue 11745015: Update references to the extension messaging APIs to point to the "runtime"

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/extensions/api/messaging/message_service.h

Issue 11745015: Update references to the extension messaging APIs to point to the "runtime" (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: rebase Created 7 years, 11 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:

View side-by-side diff with in-line comments

Download patch

« no previous file with comments | « chrome/browser/extensions/api/downloads/downloads_api.h ('k') | chrome/browser/extensions/api/messaging/message_service.cc » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: chrome/browser/extensions/api/messaging/message_service.h

diff --git a/chrome/browser/extensions/api/messaging/message_service.h b/chrome/browser/extensions/api/messaging/message_service.h

index 6e400dc4dace54ad3edfae5c70e52db6687de1ca..f4c691a0f9b4e93cd5c6be632c490f7ae0b66c8c 100644

--- a/chrome/browser/extensions/api/messaging/message_service.h

+++ b/chrome/browser/extensions/api/messaging/message_service.h

@@ -34,7 +34,7 @@ class LazyBackgroundTaskQueue;

// Messaging works this way:

// - An extension-owned script context (like a background page or a content

// script) adds an event listener to the "onConnect" event.

-// - Another context calls "extension.connect()" to open a channel to the

+// - Another context calls "runtime.connect()" to open a channel to the

// extension process, or an extension context calls "tabs.connect(tabId)" to

// open a channel to the content scripts for the given tab. The EMS notifies

// the target process/tab, which then calls the onConnect event in every