From f564d58dcdc614f94d2fc3147f24537c35a1317e Mon Sep 17 00:00:00 2001 From: Leena Miettinen Date: Fri, 29 Mar 2019 16:29:15 +0100 Subject: Doc: Avoid auto-linking the string 'WebEngine' to the QML type Remove the previous workaround (internal \externalpage command) that was used for this purpose, and replace it with a \QWE macro that expands to the string 'Qt \WebEngine'. The backslash in the expanded string instructs QDoc not to attempt auto-linking the word. Change-Id: If4e1c95423fa07479b1af055e4760a890c0ac667 Reviewed-by: Paul Wicking --- examples/webenginewidgets/webui/doc/src/webui.qdoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'examples/webenginewidgets/webui') diff --git a/examples/webenginewidgets/webui/doc/src/webui.qdoc b/examples/webenginewidgets/webui/doc/src/webui.qdoc index 47d9fbad1..949b358a7 100644 --- a/examples/webenginewidgets/webui/doc/src/webui.qdoc +++ b/examples/webenginewidgets/webui/doc/src/webui.qdoc @@ -35,8 +35,8 @@ \e {WebUI} demonstrates how to implement a custom scheme in a secure way. - Aside from the built-in URL schemes, such as \c {http} and \c {qrc}, Qt - WebEngine may be extended with \e {custom schemes} by creating \e {custom + Aside from the built-in URL schemes, such as \c {http} and \c {qrc}, + \QWE may be extended with \e {custom schemes} by creating \e {custom scheme handlers}. This example shows: \list @@ -111,7 +111,7 @@ made already at the top of the \c {main} function. This is so because custom schemes need to be registered as early as possible so that that they can be passed to all subprocesses. Specifically, custom schemes need to be registered - before any other Qt WebEngine classes are instantiated by the application. + before any other \QWE classes are instantiated by the application. \section1 Handling Requests -- cgit v1.2.3