chrome/browser/extensions/extension_test_message_listener.cc - Issue 14556015: [Media Galleries] Lazily initialize the storage monitor.

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/extension_test_message_listener.cc

Issue 14556015: [Media Galleries] Lazily initialize the storage monitor. (Closed) Base URL: http://git.chromium.org/chromium/src.git@master

Patch Set: Add StorageMonitor comment 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/extensions/extension_test_message_listener.cc

diff --git a/chrome/browser/extensions/extension_test_message_listener.cc b/chrome/browser/extensions/extension_test_message_listener.cc

index f548ac183ca7730742da8ed868bda6b8a51b25bd..a49245b55476516b96c6b5b2e3a5697c85305bf3 100644

--- a/chrome/browser/extensions/extension_test_message_listener.cc

+++ b/chrome/browser/extensions/extension_test_message_listener.cc

@@ -49,6 +49,7 @@ void ExtensionTestMessageListener::Observe(

const content::NotificationSource& source,

const content::NotificationDetails& details) {

const std::string& content = *content::Details<std::string>(details).ptr();

+ VLOG(1) << "Message from JS: " << content;

vandebo (ex-Chrome) 2013/05/31 18:05:03 Remove

Greg Billock 2013/06/01 01:48:46 Yeah. I might send this in separately, though. It

if (!satisfied_ && (content == expected_message_ ||

(!failure_message_.empty() && (content == failure_message_)))) {

if (!failed_)