From da0f1b4694d4081c62098e2587c86407f2a966f8 Mon Sep 17 00:00:00 2001 From: Nate Fischer Date: Wed, 29 Nov 2017 12:18:54 -0800 Subject: [PATCH] WebView: linkify ClientCertRequest method names No change to behavior, only docs changes. No change to wording. This linkifies ClientCertRequest method names in the docs for WebViewClient#onReceivedClientCertRequest. Test: make docs (looks good, no errors) Change-Id: I1de855e8cdf91b3aace3a188aafaa9ac9f90ed2a --- core/java/android/webkit/WebViewClient.java | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/core/java/android/webkit/WebViewClient.java b/core/java/android/webkit/WebViewClient.java index 517ad07c83235..46c39834060bd 100644 --- a/core/java/android/webkit/WebViewClient.java +++ b/core/java/android/webkit/WebViewClient.java @@ -364,13 +364,13 @@ public class WebViewClient { } /** - * Notify the host application to handle a SSL client certificate - * request. The host application is responsible for showing the UI - * if desired and providing the keys. There are three ways to - * respond: proceed(), cancel() or ignore(). Webview stores the response - * in memory (for the life of the application) if proceed() or cancel() is - * called and does not call {@code onReceivedClientCertRequest()} again for the - * same host and port pair. Webview does not store the response if ignore() + * Notify the host application to handle a SSL client certificate request. The host application + * is responsible for showing the UI if desired and providing the keys. There are three ways to + * respond: {@link ClientCertRequest#proceed}, {@link ClientCertRequest#cancel}, or {@link + * ClientCertRequest#ignore}. Webview stores the response in memory (for the life of the + * application) if {@link ClientCertRequest#proceed} or {@link ClientCertRequest#cancel} is + * called and does not call {@code onReceivedClientCertRequest()} again for the same host and + * port pair. Webview does not store the response if {@link ClientCertRequest#ignore} * is called. Note that, multiple layers in chromium network stack might be * caching the responses, so the behavior for ignore is only a best case * effort.