With the ChromeFrame moniker patch on, the data cache maintained to indicate whether we should switch to Chrome, was not being
drained correctly to the delegate, resulting in the delegate continuing to wait for more data when there was none. This caused
sites like go/wave to not redirect correctly to CF.
Fixes bug http://code.google.com/p/chromium/issues/detail?id=41365
Bug=41365
Review URL: http://codereview.chromium.org/1637017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@44735 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/chrome_frame/test/urlmon_moniker_unittest.cc b/chrome_frame/test/urlmon_moniker_unittest.cc
index f50bd86..ba1b132 100644
--- a/chrome_frame/test/urlmon_moniker_unittest.cc
+++ b/chrome_frame/test/urlmon_moniker_unittest.cc
@@ -74,7 +74,7 @@
// Test 2: Read from initialized cache
CComObjectStackEx<CacheStream> cache_stream2;
- cache_stream2.Initialize(data, sizeof(data));
+ cache_stream2.Initialize(data, sizeof(data), false);
EXPECT_HRESULT_SUCCEEDED(cache_stream2.Read(ret, sizeof(ret), &read));
EXPECT_EQ(sizeof(data), read);
EXPECT_EQ(std::string(data), std::string(ret));
@@ -112,7 +112,7 @@
Return(S_OK)));
EXPECT_HRESULT_SUCCEEDED(CacheStream::BSCBFeedData(&mock, data, size, cf,
- flags));
+ flags, false));
EXPECT_HRESULT_SUCCEEDED(ret1);
EXPECT_STREQ(data, read_buffer1);
