If we show a SafeBrowsing warning we always send the client-side detection

chrome/common/safe_browsing/safebrowsing_messages.h

Index: chrome/common/safe_browsing/safebrowsing_messages.h
diff --git a/chrome/common/safe_browsing/safebrowsing_messages.h b/chrome/common/safe_browsing/safebrowsing_messages.h
index 3d5c0b00db8c0a57626a8e5b5080f897357bdcc7..c5af23a67ce7ced156c9e1c9bee1fc61af6ebfd1 100644
--- a/chrome/common/safe_browsing/safebrowsing_messages.h
+++ b/chrome/common/safe_browsing/safebrowsing_messages.h
@@ -28,11 +28,12 @@ IPC_STRUCT_END()
 // SafeBrowsing client-side detection messages sent from the renderer to the
 // browser.
 
-// Inform the browser that the URL in the given ClientPhishingRequest proto is
-// phishing according to the client-side phishing detector.
+// Inform the browser that the client-side phishing detector running in the
+// renderer is done classifying the current URL.  If the URL is phishing
+// the request proto will have |is_phishing()| set to true.
 // TODO(noelutz): we may want to create custom ParamTraits for MessageLite to
 // have a generic way to send protocol messages over IPC.
-IPC_MESSAGE_ROUTED1(SafeBrowsingHostMsg_DetectedPhishingSite,
+IPC_MESSAGE_ROUTED1(SafeBrowsingHostMsg_PhishingDetectionDone,
                     std::string /* encoded ClientPhishingRequest proto */)
 
 // Send part of the DOM to the browser, to be used in a malware report.