Credential Manager: Renderer-side implementation.

content/renderer/renderer_webkitplatformsupport_impl.cc

Index: content/renderer/renderer_webkitplatformsupport_impl.cc
diff --git a/content/renderer/renderer_webkitplatformsupport_impl.cc b/content/renderer/renderer_webkitplatformsupport_impl.cc
index c150e0c624ae7bda6806483818d2a117c2a8e005..54dde34b8ee1371f064342c6e16038c782742296 100644
--- a/content/renderer/renderer_webkitplatformsupport_impl.cc
+++ b/content/renderer/renderer_webkitplatformsupport_impl.cc
@@ -872,6 +872,13 @@ WebBlobRegistry* RendererWebKitPlatformSupportImpl::blobRegistry() {
 
 //------------------------------------------------------------------------------
 
+blink::WebCredentialManager*
+RendererWebKitPlatformSupportImpl::credentialManager() {
+  return GetContentClient()->renderer()->GetCredentialManager();

[jam, 2014/08/19 19:55:31]

the pattern we had used for the content refactoring is that interfaces which
blink needs and that are implemented by chrome are set directly by chrome. that
way we dont have to go through content just to ask chrome. as an example, see
ChromeContentRendererClient::RenderViewCreated which creates a bunch of classes.
in their constructors, tehy do something like
render_view->GetWebView()->setFooClient

[Mike West, 2014/08/20 13:17:20]

That keeps //content clean at the expense of making Blink a bit more complex,
which is a shame. :( *shrug* Regardless, I've uploaded
https://codereview.chromium.org/488993003/ to prepare for moving things around
in this patch.

+}
+
+//------------------------------------------------------------------------------
+
 void RendererWebKitPlatformSupportImpl::sampleGamepads(WebGamepads& gamepads) {
   DCHECK(gamepad_provider_);
   gamepad_provider_->SampleGamepads(gamepads);