Observe visibility of password inputs, for HTTP-bad phase 1

third_party/WebKit/Source/web/ChromeClientImpl.cpp

Index: third_party/WebKit/Source/web/ChromeClientImpl.cpp
diff --git a/third_party/WebKit/Source/web/ChromeClientImpl.cpp b/third_party/WebKit/Source/web/ChromeClientImpl.cpp
index ddb64a39b87ba664bb7fbf7f9063af5db0fb94ec..a327f24f83f3ee995289da9ab7c9b1126d744b81 100644
--- a/third_party/WebKit/Source/web/ChromeClientImpl.cpp
+++ b/third_party/WebKit/Source/web/ChromeClientImpl.cpp
@@ -1070,6 +1070,13 @@ void ChromeClientImpl::ajaxSucceeded(LocalFrame* frame)
         webframe->autofillClient()->ajaxSucceeded();
 }
 
+void ChromeClientImpl::passwordFieldBecameVisible(HTMLInputElement& input)
+{
+    WebLocalFrameImpl* webframe = WebLocalFrameImpl::fromFrame(input.document().frame());
+    if (webframe->autofillClient())
+        webframe->autofillClient()->passwordFieldBecameVisible();

[esprehn, 2016/09/27 23:30:19]

Please use mojo directly instead, I don't want to plumb out more callbacks.

[estark, 2016/09/27 23:35:42]

Can you point to an example of what you mean by "use mojo directly"? I'm a mojo
noob and am not sure what that means.

[estark, 2016/09/27 23:39:42]

Oh, actually, I just found and am reading
https://dev.chromium.org/developers/design-documents/mojo/calling-mojo-from-b...
and have a feeling that will answer my question. :)

+}
+
 void ChromeClientImpl::registerViewportLayers() const
 {
     if (m_webView->rootGraphicsLayer() && m_webView->layerTreeView())