From d0725820c3f55aea3789489a64c63cc0b79325ff Mon Sep 17 00:00:00 2001 From: Kai Koehne Date: Fri, 16 Aug 2019 15:40:32 +0200 Subject: Doc: Mention QML API for client certificates WebEngineView.selectClientCertificate is new API in Qt 5.13. Add a link to the signal in the 'Client Certificate' section of the 'Qt WebEngine Features' page. Change-Id: Ie347973d8f9657870e975adde089e3d9d0abd6d4 Reviewed-by: Allan Sandfeld Jensen --- src/webengine/doc/src/qtwebengine-features.qdoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'src/webengine') diff --git a/src/webengine/doc/src/qtwebengine-features.qdoc b/src/webengine/doc/src/qtwebengine-features.qdoc index 08c189740..00b9cb496 100644 --- a/src/webengine/doc/src/qtwebengine-features.qdoc +++ b/src/webengine/doc/src/qtwebengine-features.qdoc @@ -126,7 +126,9 @@ so uniquely identifies the user and might violate privacy expectations. To activate support for client certificates, an application needs to listen to - the QWebEnginePage::selectClientCertificate signal and select one of the offered + the QWebEnginePage::selectClientCertificate or + \l{WebEnginePage::selectClientCertificate}{WebEnginePage.selectClientCertificate} + signals and select one of the offered certificates. For applications that can navigate to untrusted web sites, it is recommended to always give the user a choice before uniquely identifying them to a remote server. -- cgit v1.2.3