aboutsummaryrefslogtreecommitdiffstats
path: root/doc/src/qml/security.qdoc
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/qml/security.qdoc')
-rw-r--r--doc/src/qml/security.qdoc16
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/src/qml/security.qdoc b/doc/src/qml/security.qdoc
index 262e560d33..190d6930c5 100644
--- a/doc/src/qml/security.qdoc
+++ b/doc/src/qml/security.qdoc
@@ -61,21 +61,21 @@ perform appropriate checks on untrusted data it loads.
A non-exhaustive list of the ways you could shoot yourself in the foot is:
\list
- \i Using \c import to import QML or JavaScript you do not control. BAD
- \i Using \l Loader to import QML you do not control. BAD
- \i Using \l{XMLHttpRequest}{XMLHttpRequest} to load data you do not control and executing it. BAD
+ \li Using \c import to import QML or JavaScript you do not control. BAD
+ \li Using \l Loader to import QML you do not control. BAD
+ \li Using \l{XMLHttpRequest}{XMLHttpRequest} to load data you do not control and executing it. BAD
\endlist
However, the above does not mean that you have no use for the network transparency of QML.
-There are many good and useful things you \i can do:
+There are many good and useful things you \e can do:
\list
- \i Create \l Image elements with source URLs of any online images. GOOD
- \i Use XmlListModel to present online content. GOOD
- \i Use \l{XMLHttpRequest}{XMLHttpRequest} to interact with online services. GOOD
+ \li Create \l Image elements with source URLs of any online images. GOOD
+ \li Use XmlListModel to present online content. GOOD
+ \li Use \l{XMLHttpRequest}{XMLHttpRequest} to interact with online services. GOOD
\endlist
-The only reason this page is necessary at all is that JavaScript, when run in a \i{web browser},
+The only reason this page is necessary at all is that JavaScript, when run in a \e{web browser},
has quite many restrictions. With QML, you should neither rely on similar restrictions, nor
worry about working around them.
*/