diff options
| author | Sze Howe Koh <szehowe.koh@gmail.com> | 2013-04-04 16:18:30 +0000 |
|---|---|---|
| committer | The Qt Project <gerrit-noreply@qt-project.org> | 2013-04-05 12:55:08 +0200 |
| commit | 4378e48208f76ec39fdb32dbdbb0e03dd804bf65 (patch) | |
| tree | 8d33de9b8b2cdcbf3d90b9b1aff0eaead061e5ee /Source/WebKit/qt/WidgetApi/qwebframe.cpp | |
| parent | cef77ac6846fa60b3baa5731164c5efca651becb (diff) | |
| download | qtwebkit-4378e48208f76ec39fdb32dbdbb0e03dd804bf65.tar.gz | |
[Qt] docs: Fix module name format
https://bugs.webkit.org/show_bug.cgi?id=113209
Reviewed by Jocelyn Turcotte.
Make QDoc-generated documentation follow the conventions at
http://qt-project.org/wiki/Spelling_Module_Names_in_Qt_Documentation
Source/WebKit/qt:
* Api/qwebdatabase.cpp:
* Api/qwebkitglobal.cpp:
* Api/qwebpluginfactory.cpp:
* Api/qwebsettings.cpp:
* WidgetApi/qgraphicswebview.cpp:
* WidgetApi/qwebframe.cpp:
* WidgetApi/qwebpage.cpp:
* WidgetApi/qwebview.cpp:
* docs/qtwebkit-bridge.qdoc:
* docs/qtwebkit-goes-mobile.qdoc:
* docs/qtwebkit.qdoc:
Source/WebKit2:
* UIProcess/API/qt/qquickwebview.cpp:
Change-Id: I27927b6a3722f86379fdc538a53f4cc84c68494f
git-svn-id: http://svn.webkit.org/repository/webkit/trunk@147637 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Reviewed-by: Simon Hausmann <simon.hausmann@digia.com>
Diffstat (limited to 'Source/WebKit/qt/WidgetApi/qwebframe.cpp')
| -rw-r--r-- | Source/WebKit/qt/WidgetApi/qwebframe.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Source/WebKit/qt/WidgetApi/qwebframe.cpp b/Source/WebKit/qt/WidgetApi/qwebframe.cpp index 242edb1ea..e7286f88e 100644 --- a/Source/WebKit/qt/WidgetApi/qwebframe.cpp +++ b/Source/WebKit/qt/WidgetApi/qwebframe.cpp @@ -242,7 +242,7 @@ QWebFrame::~QWebFrame() Qt properties will be exposed as JavaScript properties and slots as JavaScript methods. - The interaction between C++ and JavaScript is explained in the documentation of the \l{The QtWebKit Bridge}{QtWebKit bridge}. + The interaction between C++ and JavaScript is explained in the documentation of the \l{The Qt WebKit Bridge}{Qt WebKit bridge}. If you want to ensure that your QObjects remain accessible after loading a new URL, you should add them in a slot connected to the |