| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
This generates more compact code. It also fixes a build issue with
some disabled features on macOS.
Task-number: QTBUG-63440
Change-Id: Ice800bdfef09dd83310d40cadd37c15c846ca3e1
Reviewed-by: Viktor Engelmann <viktor.engelmann@qt.io>
Reviewed-by: Christian Stromme <christian.stromme@qt.io>
(cherry picked from commit 3bcd4c3506c9352874f1403aba22e36108a867a2)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QQuickViewChangeListener::itemParentChanged is called for parent
changes done to any of the items we listen to up the parent chain.
But as it stood, we would always remove the change listener from
m_item->parentItem(), even if the changed item was higher up in
the hierarchy. We would therefore wrongly miss any later changes
done to m_item->parentItem().
A bug from this could be seen when pushing an item containing a
webview to a stackview, since then, several parent changes would
occur.
[ChangeLog][General] Fixed missing geometry update bug when a
webview changed anchestor (e.g. when pushing it onto a StackView).
Task-number: QTBUG-54128
Change-Id: Iff00a0029dd713306db7e39db8c92672a6b379c7
Reviewed-by: Christian Stromme <christian.stromme@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
Don't delay initialization until we're inserted into the scene, as this
will cause every property change/function call that happens before that
to be dropped.
Task-number: QTBUG-53839
Change-Id: I1a2f9066c7b172e14095d7513f343e34812f7d1a
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
| |
QQuickViewChangeListener wasn't cleaning up its ancestor listeners
properly. QQuickItemChangeListener::itemChildRemoved() is too late
for removing listeners of the _ancestors_ of the child that just
got removed.
Task-number: QTBUG-55127
Change-Id: I004a5dd0b49fa36baabf951ee41d8a9ccdef4da8
Reviewed-by: Christian Stromme <christian.stromme@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Since Android 5.0 Google introduce a nasty bug[1] which calls
JNI_OnLoad more than once.
Basically every time when a library is loaded JNI_OnLoad is
called if found, but it calls *again* JNI_OnLoad of its .so
dependencies!
[1] Workaround https://code.google.com/p/android/issues/detail?id=215069
Change-Id: I87b50b67d7c63a32b3fae067a78780a17b058acb
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
When resizing, the device pixel ratio needs to be taken into account.
Otherwise the area for Xaml viewer will be misplaced and/or wrongly
scaled.
Change-Id: Id2dd34c2dd29f5582a9f3536e6394c7e49eddf94
Task-number: QTBUG-53405
Reviewed-by: Oliver Wolff <oliver.wolff@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Android WebView does not handle schemes by default, such
as mailto:, geo:, and others, but will instead show an
"ERR_UNKNOWN_URL_SCHEME" error. This patch fixes it by
starting ACTION_VIEW Intent for specified scheme, meanwhile
showing the same "ERR_UNKNOWN_URL_SCHEME" error page for
invalid cases as before.
[ChangeLog][Android] Added support for various url schemes.
Taks-number: QTBUG-53736
Change-Id: Ib569ec1598f76f823b2293446ea4e513764ef1fa
Reviewed-by: Christian Stromme <christian.stromme@qt.io>
|
| |
|
|
|
|
|
|
| |
Enable automatic linking to Qt GUI module.
Task-number: QTBUG-53560
Change-Id: Id22a4a42c038dcbda939b170f9f7c0ae93d6b18b
Reviewed-by: Topi Reiniö <topi.reinio@theqtcompany.com>
|
| |
|
|
|
|
|
|
| |
Examples in binary packages now directly match the install path.
Change-Id: Ie631ed16dc0e7b3f30940a0f2c0749a90a51c027
Task-number: QTBUG-52953
Reviewed-by: Antti Kokko <antti.kokko@qt.io>
|
| |
|
|
|
|
|
|
| |
Move the common, and QtQuick specific code, into the view controller
to make the behavior more consistent across all platforms.
Change-Id: I89cc383fb92ee6755e8fba9baf48e3e756d04cca
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When High DPI mode is enabled, with a scale different then 1, the values
we get are not in the same scale as setClipBounds expects. While it is
possible to convert the values to native pixel first, it's probably
better if we just disable this functionality on Android, that is, until
a better cross-platform solution can be found.
Task-number: QTBUG-51198
Change-Id: Ia3e3e3911b9ba24d83e49afa6bec61696b93073a
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |\
| |
| |
| | |
Change-Id: I7abf6d60ff1738d669f6761b20af380cbf2b4140
|
| | |
| |
| |
| |
| | |
Change-Id: Iad7e39cf5a986909bc0e5dcb9a82143b2e9ed260
Reviewed-by: Yoann Lopes <yoann.lopes@theqtcompany.com>
|
| | |
| |
| |
| |
| | |
Change-Id: I595eac8877100f35289d42f875ffc6e506774b4f
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>
|
| | |
| |
| |
| |
| |
| |
| | |
.qmake.conf already does that.
Change-Id: I88dd34c05f6326f733d23a0a66bdea5853d5beb1
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This removes the need for the awkward type re-registering and renaming
that was done in the Qml plugin, to support QtWebEngine.
Among other issues, the main motivation for this change is to unify the
implementations, and make it possible to run the auto tests that
interfaces directly with the QQuickWebView class. Having an actual
backend for Qt WebEngine means we can get rid of the, non-functional,
default implementation as well.
Change-Id: Ia93611ed2755c92207ca86ba3890ac4c2c4d72e9
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When setting the parent view of the WebvView we need to use the real
window, and not the off-screen window provided by QQuickWidget.
This change also improves the logic for setting the geometry, as extra
care is needed to make sure the view is position correctly inside the
scene when using a QQuickWidget.
Task-number: QTBUG-48221
Change-Id: I476cac926df6c862cc3602b21e97003cc254726c
Reviewed-by: Timur Pocheptsov <timur.pocheptsov@theqtcompany.com>
|
| | |
| |
| |
| |
| |
| |
| | |
Caught by -Winconsistent-missing-override
Change-Id: I96203ea1bd0c9396bc361e0df4e507d1f12f02f4
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Loading content through the Qt Resource System is not supported by us
or the different backends, so we should document it as a limitation.
Task-number: QTBUG-49698
Change-Id: Ibe237987682894957cb34778389fc4ffb3facdb2
Reviewed-by: Venugopal Shivashankar <venugopal.shivashankar@digia.com>
|
| | |
| |
| |
| |
| | |
Change-Id: Iafc4f49a0e7a5aee6aef0622142271000b8f82e8
Reviewed-by: Maurice Kalinowski <maurice.kalinowski@theqtcompany.com>
|
| |/
|
|
|
| |
Change-Id: Iab424566018aaeac1f26d3802f79c1d7b83bad06
Reviewed-by: Christian Stromme <christian.stromme@theqtcompany.com>
|
| |
|
|
|
| |
Change-Id: Ia656aacc021fc063a1ed87acc02cccba1cc9edf7
Reviewed-by: BogDan Vatra <bogdan@kdab.com>
|
| |
|
|
|
| |
Change-Id: Ia692190470423d8db82fd6c27f4c9ad06223c438
Reviewed-by: Christian Stromme <christian.stromme@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The WebView will continue to evaluate JavaScript even after we've
released all handles to the WebView, to avoid this we'll call destroy()
when we release the WebView on our side. On Android 6.0 there's issued
a warning when destroy is called, but this is not fatal and seems to
be a know issue on their side. Alternatively, if it turns out that
calling destroy() causes problems in the future, it's possible to stop
JS evaluation by disabling it through the WebSettings interface.
Task-number: QTBUG-49664
Change-Id: Ic98d24d58525397ad06ecbc4476cd5613b6663ab
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Webapps dependent on geolocation fails even if ACCESS_FINE_LOCATION
permission is set by developer for the package itself. This fix
implements implicit user prompt to allow access to geolocation
data if ACCESS_FINE_LOCATION permission is set. From now on,
QtWebView adds ACCESS_FINE_LOCATION by default to make it work out
of the box. Packages built without ACCESS_FINE_LOCATION (if developer
removes it manally) will not (naturally) get access to device
location as before this fix, nor there will be Android security
exceptions.
Task-number: QTBUG-49566
Change-Id: I476aef28e59f238a571ed77984b9cd294a9bbd25
Reviewed-by: Christian Stromme <christian.stromme@theqtcompany.com>
|
| |
|
|
|
| |
Change-Id: Idf832c54278c27f1658913fa1956fcb5fdbe39dc
Reviewed-by: Christian Stromme <christian.stromme@theqtcompany.com>
|
| |
|
|
|
|
|
| |
Was wrongly identified as closing comment by MSVC2015.
Change-Id: If2b89c9ace7b8a950852765e55a73fd154f945a9
Reviewed-by: Christian Stromme <christian.stromme@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
| |
Respect statusbar size when setting webviews geometry.
Change-Id: Ifae03d2a673930a97ce1726cb50dd19ef6a1f7bb
Task-Id: QTBUG-48842
Reviewed-by: Andrew Knight <andrew.knight@intopalo.com>
Reviewed-by: Maurice Kalinowski <maurice.kalinowski@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Document WebView.loadingChanged() signal
- Use QT_VERSION everywhere in .qdocconf
- Fix QDoc warnings, linking issues
- Mark read-only QML properties as \readonly
- Minor language edits
Change-Id: Ieb9625d81aaee73a236222b85a496ee5783b644e
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@theqtcompany.com>
Reviewed-by: Christian Stromme <christian.stromme@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
| |
Document the QtWebView module, add the Q_WEBVIEW_EXPORT macro to
.qdocconf, edit the help project sections and link to the
C++ module documentation from the overview.
Change-Id: I3deb34e8067278915610e24a15baf52e365629fb
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@theqtcompany.com>
Reviewed-by: Christian Stromme <christian.stromme@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The examplesinstallpath variable in .qdocconf files defines the path
under QT_INSTALL_EXAMPLES where examples are found.
To match the way examples are packaged in Qt 5.6, prefix the
install path with the repository name.
Task-number: QTBUG-48736
Change-Id: Ifbd5d702aa0c5cdad100bcbc88515e3e5c3c0eed
Reviewed-by: Venugopal Shivashankar <venugopal.shivashankar@digia.com>
|
| |
|
|
|
|
|
|
|
|
| |
This change reverts back to using Qt WebEngine as a backend on OS X, as
there are still challenges that needs to be solved when using the
native WebView implementation, e.g., make it possible to use it without
disabling batched rendering.
Change-Id: I9cc95233990055d59480ad4d47ebf3da4ebb07f1
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
| |
Registration of the WebView item should be done with qmlRegisterType and
not qmlRegisterRevision, as the later is not intended for classes that
are publicly exported and will therefore not be inserted into the
.qmltypes file.
Change-Id: I9ce3b9551b93243a139527e730466ae4aafd73b0
Reviewed-by: Yoann Lopes <yoann.lopes@theqtcompany.com>
|
| |
|
|
|
|
|
|
| |
We need to include the header for QByteArray, as it's required when
calling qputenv().
Change-Id: I245d769b050525719dc6db202a6724ce887ba4a7
Reviewed-by: Yoann Lopes <yoann.lopes@theqtcompany.com>
|
| |
|
|
|
| |
Change-Id: I8fc55d1c4e82e9a635107b8adc40c143f405eb93
Reviewed-by: Frederik Gladhorn <frederik.gladhorn@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
| |
Two files were using old LGPL license headers and that's why license
header tests were failed. Changed those files to use LGPLv3 header
template
Change-Id: I95bd010087b83c6aa174d53e7c2378bdd9e57c70
Reviewed-by: Simon Hausmann <simon.hausmann@theqtcompany.com>
|
| |
|
|
|
|
|
|
| |
Now that WinRT uses XAML-based windows, it can support creating native
WebView controls.
Change-Id: I04361956eba9de5b5d41fcc6b57a9772b49f6a2b
Reviewed-by: Christian Stromme <christian.stromme@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The initialization function will set-up any platform specific
requirements needed to display the WebView correctly.
Initially we tried to avoid this, as it's not a very nice approach, and
it was only needed when QtWebEngine back-end was the used (see:
QtWebEngine::initialize()). Since we now require special set-up for OS X
as well, it has become unreasonable to expect that the user should
implement this logic in their application and that it's more convenient
if we provide a uniform solution to make the WebView work on all
platforms.
The implication of this change, is that we now actually expose a C++ API
and will therefore need to export the module again
(making it a non-internal module).
Change-Id: I87678db7cd50b25465bcf623c008f04a4cffd7df
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
|
|
|
|
|
|
| |
Since these classes won't be part of the public API any time soon, it's
better that we just make them as private.
Change-Id: Id3c1aeb0ad537a1630a04f669a2d4feb09d8b2e1
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
|
|
|
|
|
| |
Replaces the last slots keyword in the code with Q_SLOTS.
Change-Id: I1da5abc612eb00cbc56c9e483c555460c7021880
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
|
|
|
|
|
|
| |
We need to set scalesPageToFit to enable user zooming.
Task-number: QTBUG-46211
Change-Id: Ibf114a6571fb7cf57564b8f22e044efc5ff32381
Reviewed-by: Christian Stromme <christian.stromme@theqtcompany.com>
|
| |
|
|
|
|
|
| |
Changed liseners -> listeners
Change-Id: I8d06866fe13a48280cda80f1f0b7757dc9a3b0cb
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
|
|
|
|
|
|
| |
Remove the listener from the old parents when a new parent is set or
when the controller item is destroyed.
Change-Id: If4cf2bf1d2a209514f9f37028e5210335f418dc7
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
| |
We should always send the the starting request update, so we always
transition from starting and go to finished or error even if the url
is invalid or can't be reached.
Change-Id: I4e917b95bf34e44bd8986bdccd2fb2f5aa183414
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
|
|
|
|
|
| |
Fixes problems were isLoading() would return the wrong value.
Change-Id: I0e0876551f9dcbd41523731dd51dce806680c10e
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
|
|
|
| |
Change-Id: I494097e6cf61ab46abc113422a5c250b529b4a3d
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
|
|
|
| |
Change-Id: Id046571bd3e115904491465f8693338b40a336ac
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
|
|
|
| |
Change-Id: Iabddc9c1016626807a1860c76f0ebbc3170a7b7a
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We block the Android UI thread when we call into the native WebView
which means it's possible to deadlock or cause the
"Application Not Responding" handler to be activated, e.g., if the
WebView or UI thread is unable to process the request quickly enough.
This change makes sure we never block the UI thread for longer then
250ms. Anything beyond 200ms is and we can be certain the UI thread is
overloaded or we're blocking both the Qt thread and the Android thread.
Change-Id: I237674091e4d5db80209b5295f75b61e886f3db4
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
The QWebView and QWebViewPrivate class are now in the object tree and
will therefore be delete once their parent is destroyed.
This change removes the QScopedPointers that used to manage the
lifetime of the webview instances.
Task-number: QTBUG-46286
Change-Id: I2d7f12b317770113e5b35c14b60df7442aa3e68e
Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@theqtcompany.com>
|