| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
Change-Id: Ia90ec9c91315c18bdd4d8906608d5579843a56ca
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
|
|
|
| |
Submodule src/3rdparty 031a1067..d60a9e56:
* [clang] Pass -fno-pch-timestamp to all clang targets
Change-Id: Idd69de331398ad061a2e413fb02aaff9047220b0
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
|
|
|
|
|
|
|
| |
Fixing link for
https://doc-snapshots.qt.io/qt6-dev/qwebengineglobalsettingsdnsmode.html
Pick-to: 6.11
Change-Id: I78d9f78741ee1d750f2ec41a9e9329afadf2a787
Reviewed-by: Moss Heim <moss.heim@qt.io>
|
| |
|
|
|
| |
Change-Id: I38c7fb4673801767575643ac4e62bed00594997f
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
| |
Change-Id: I1ea9509d73c6948ec5407a589f8df7d4768b5b87
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
| |
Change-Id: Ief0a36eeb24b63a19b7d3307a8c13b2222a72f53
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the popup window has the Qt::Dialog flag, some window managers may
try to resize and move the popup after it becomes visible. This can lead
to a blinking popup or even worse, it can cause a loop that continuously
moves the popup window.
Replace Qt::Tool flag with Qt::Popup to get rid of the Qt::Dialog flag
but keep popup as popup.
Note on Wayland Qt:Tool is xdg toplevel not a 'popup' neither 'grabbing
popup' and it creates shell surface. This means it will get random
position on the screen.
Note this tricky issue as we already changed that several times both
for widgets and quick due to different reasons (see 1390979a, 2f720836,
58467ed19, 7e7dd2625, c56169f7a1)
Fixes: QTBUG-140321
Task-number: QTBUG-132794
Task-number: QTBUG-138747
Pick-to: 6.10
Change-Id: I8c3a94519008455fac2d8ab4c3bf34d860e2475b
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch is band-aid patch to handle QQuickWebEngineView
transformations like scaling and rotation.
Before this patch we used mapToGlobal to get viewGeometry
however if the item is transformed by rotation and
scaling the mapToGlobal will return something not expected by
Chromium. Imagine:
--------- -------
| aaaaa | | aaaa|
| bbbbb | => rotates 90 => | bbbb|
| ccccc | | cccc|
--------- | |
-------
So Chromium still 'thinks' that content is displayed
horizontally and just window geometry changed.
Moreover, mapToGlobal for rect QRectF(tl,rb) when this is
rotated by 90 degree will return QRectF(tr,bl).nomralized()
in global coordinates. This is not correct geometry.
As band-aid solution for transform case, go with
fixed view geometry of QRect(0,0,widith(),hight())
This will allow to Chromium get untransformed popup position,
which we later transform in delegate. Fix and simplify
transformation calculations in QQuickWindow delegate
using just global screen coordinates.
Note having fixed view geometry will have side effect
like accessibility mappings broken or screen edge detection
not working (if dropdown comobox can not be displayed due to
screen border it is simply moved over the combobox filed)
Therefore, this is just band-aid solution, which covers anyway
rare use case of doing the QQuickWebview transformation
within the scene.
Tested with openbox, weston, mutter-wayland, mutter-xwayland.
Pick-to: 6.10
Change-Id: I3c2d662ccd093793da6b5e192d79c9e22e451789
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
During transition from Qt5 to Qt6, we moved some code to
core and in 5d1ef38f9 we moved RWHV delegate to core.
Before that change we used to feed chromium with geometry
and frame geometry of delegated window and later in case
of qquickwindow based delegate we did dome extra 'fixup'
calculations to cover the fact that using geometry()
for view geometry in screen coordinates did not include
actual item delegate offset from the qml scene.
However after the change we use simply mapToGlobal within
the delegate for view geometry which already knows exact
global coordinates for the item within the qml scene.
In e2185036 we have fix for accessibility layout,
however local coordinate mappings makes no sense as it
will always return "0".
this->mapFromItem(this,QPoint(0,0))
Use simply global coordinates here, and remove obsolete
"fixup" calculation for offset in qquickwindow delegate.
Note this patch does not care about rotated qquickwebengineview.
The band-aid patch for that is in followup.
Task-number: QTBUG-135040
Fixes: QTBUG-140321
Fixes: QTBUG-139709
Pick-to: 6.10
Change-Id: I01266b42bc74120e39e2703db78c2b9c3548572f
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Chromium needs to be aware of view geometry changes.
We do the sync in visualPropertiesChanged call, which
in turn is called from item geometryChanged and
itemChanged handlers.
However, this approach is not sufficient to track global
geometry changes as it only covers case where geometry change is
local to item's parent.
Therefore, we need watch the entire parent hierarchy
to correctly handle global geometry change notifications.
Note this issue only affects webenginequick as
rwhv can have offset from the scene due to explicit
position or anchoring within other items.
Moreover, anchoring of child item can mean
making offset in parent item.
Add logic to track offset changes of parent items.
Use 'polish' accumulate required notification and
do visualPropertiesChanged() in updatePolish() call.
Fixes: QTBUG-141476
Pick-to: 6.10
Change-Id: Ia35a6f243624cb06b6b45f76abf8ba544790e2c0
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
|
| |
|
|
|
| |
Change-Id: I3f2de6f0e607b53028c9830a68b861c1a087d3b4
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The clean job can be scheduled too late and compositor can
be already unbinded and deleted. This sadly can leak resources.
Synchronize therefore gpu thread and render thread and wait
for clean up job to unbind before unbinding the compositor.
Task-number: QTBUG-141739
Pick-to: 6.10 6.9
Change-Id: I071cd244dc6169d6059b84500226a9175aded1f4
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Do not move compositor handle, make a clean job
a compositor observer instead. This prevents
the deadlock.
Fixes: QTBUG-141739
Fixes: QTBUG-141214
Pick-to: 6.10 6.9 6.8
Change-Id: Ic51ce467ec65ae3cb1ae556328cf8eb171fe59a0
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
|
| |
|
|
|
|
|
|
|
|
| |
The machinery is quite complicated, so adding comments that explain it
helps when looking at it in the future.
Pick-to: 6.8 6.10
Task-number: QTBUG-116619
Change-Id: Ic3ee295f8e0f46438e2cfa6f04f921ecac5a5dee
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
| |
|
|
|
| |
Change-Id: I3254c3e7983045573f88162e162b32ba1736f82d
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We use CorsURLLoader since the 124-based Chromium. This performs a
safety check on calling CorsURLLoader::OnReceiveRedirect(), since
fetch() requests have more strict rules when accessing cross origin
resources.
This patch extends our dummy response with the Allow-Origin header
(only in case of redirects), so the request interceptor API users
won't hit this wall.
Test case implemented by: Benjamin Terrier
Task-number: QTBUG-140889
Change-Id: I8b1d2a94d4157c9d42684398fa69425e5706905d
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
| |
Submodule src/3rdparty f9d3b37ec..031a10673:
> [sbom] Fix SBOM generation for non-git builds
> [Backport] Security bug 460017370
> [Backport] CVE-2025-13042: Inappropriate implementation in V8
Pick-to: 6.10
Change-Id: Ie66af6ba3e5d454bcc38e873b785df63060f91e8
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bail out earlier and do not crash in navigationRequested callback
when qmlEngine is null. This may happen when using WebEngineView e.g.
in a Loader, as the QML context data is cleared before the object is
destroyed and accordingly, before we unsubscribe from the callback.
Note this is band aid fix, as it is still unclear why this problem
did not occur here before (e.g. with Qt 6.8.3).
Task-number: QTBUG-137768
Pick-to: 6.10
Change-Id: I33bbaf4240511d20f0b839317fb496fd5b270006
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This is to be used in QWebView, where the WebEngine backend is
based on our Quick API. With the addition of a C++ WebView API,
we need a way to call C++ callbacks, and the JavaScript-based callback
mechanism that's currently there is insufficient.
We can't expose an std::function parameter to QML, so this overload
is there for internal use only.
Change-Id: I22b17c2d2ba554078d0e1e39110147399e93102b
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
|
|
|
| |
Change-Id: Ida12ff589a2aaff1d8ebf5f4f82135e5b1eb43e5
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a page is destroyed during printing, there is no view to emit
printFinished() and yet the printer thread continues in the background
until the job is finished.
We can improve things somewhat by requesting an interrupt and exiting
early in the printer worker thread. Then at least users do not wait
around forever for the printer to be idle and deleteable.
Add tests both for this case and basic printing with `print(QPrinter*)`
Task-number: QTBUG-140232
Pick-to: 6.8 6.10
Change-Id: If43677b7ad8021d72dd945fd36c3263234692b95
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
|
|
|
| |
Change-Id: Ie8c31712d26213b8dc211ec41a31df9098163b81
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
| |
Change-Id: I7cfc2729f0504855864b6b60e9742fe0a03a3804
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
| |
Change-Id: I409db29636eefef72df318ea336f4c33edd04e68
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
| |
Change-Id: I16d4e14315c9e8dd2c3f4bdd84a602909ff1ec02
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
| |
Change-Id: I32b8ef90a22446162f3bcd2f3271cb1b57f5b669
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Submodule src/3rdparty 898da6a2..f9d3b37e:
* [revert] Revert "Fix clang + bfd linker build"
* [fixup] Jumbo build
* [fixup][backport] CVE-2025-6021
* [Backport] CVE-2025-12036: Inappropriate implementation in V8 (3/3)
* [Backport] CVE-2025-12036: Inappropriate implementation in V8 (2/3)
* [Backport] CVE-2025-12036: Inappropriate implementation in V8 (1/3)
* [fixup] Fix QtWebEngine build on all platforms
* [Backport] CVE-2025-12726: Inappropriate implementation in Views (3/3)
* [Backport] CVE-2025-12726: Inappropriate implementation in Views (2/3)
* [Backport] CVE-2025-12726: Inappropriate implementation in Views (1/3)
* [Backport] CVE-2025-12432: Race in V8
* Fix clang + bfd linker build
* CVE-2025-12429: Inappropriate implementation in V8
* [Backport] CVE-2025-12438: Use after free in Ozone
* [Backport] CVE-2025-12441: Out of bounds read in V8
* [Backport] CVE-2025-12433: Inappropriate implementation in V8
* [Backport] CVE-2025-12443: Out of bounds read in WebXR
* [fixup] Fix QtWebEngine build on all platforms
* [Backport] CVE-2025-24928
* [Backport] CVE-2025-6021
* [Backport] IWYU modules/desktop_capture and modules/video_capture for PipeWire
* [Backport] IWYU modules/video_capture
* [Backport] CVE-2025-11756: Use after free in Safe Browsing
* [Backport] CVE-2025-11460: Use after free in Storage
* [Backport] CVE-2025-11458: Heap buffer overflow in Sync
* [Backport] Security bug 40059598 (5/5)
* [Backport] Security bug 40059598 (4/5)
* [Backport] Security bug 40059598 (3/5)
* [Backport] Security bug 40059598 (2/5)
* [Backport] Security bug 40059598 (1/5)
* [Backport] Dependency for security bug 40059598
* [Backport] Security bug 434161973
* [Backport] CVE-2025-11216: Inappropriate implementation in Storage
* [Backport] CVE-2025-11207: Side-channel information leakage in Storage (2/2)
* [Backport] CVE-2025-11207: Side-channel information leakage in Storage (1/2)
* [Backport] CVE-2025-11219: Use after free in V8
* [Backport] Security bug 440866282
* [Backport] CVE-2025-6965 / Security bug 434161973
* [Backport] Security bug 435225528
* [Backport] Security bug 439058241
* [Backport] Security bug 441427753
* [Backport] CVE-2025-11206: Heap buffer overflow in Video
* [fixup][gcc-10] Fix compilation issue with gcc-10
* [fixup] Workaround for not working pointer traits on clang-15, gcc-10 and msvc19
* Revert "[fixup][gcc-10] Fix compilation issue with gcc-10"
* [Backport] Disable NSAutoFillHeuristicController on macOS 26
Fixes: QTBUG-141153
Fixes: QTBUG-141795
Fixes: QTBUG-141796
Change-Id: I601ec0a302f97d0d8d297a07e4a5455e876fb440
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
(cherry picked from commit 971519b7c5dd23ea27fc091dd5837bc6d1cb2ede)
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
|
|
|
| |
Change-Id: Ib65b06e00f628fcdfa214d694dda59118150aec6
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
| |
Change-Id: I1f5ab651da9c959ad3f8d82581482c4d13805201
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
| |
Change-Id: If027d9efd49280d23703b4d9edd625537f517042
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
| |
This reverts commit 48ba78f27354a0252d09410203ce4191d6129d57.
Reason for revert: <New test is flaky>
Change-Id: I563e53390999f76ff5582de5750f102eb7d42964
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
|
|
|
|
|
|
|
| |
QT_NO_AS_CONST got renamed in qtbase.git in commit
03baf08d2bb9
Task-number: QTBUG-141558
Change-Id: I21614ef8a087609918ae79e5c54651e358f2a587
Reviewed-by: Kai Köhne <kai.koehne@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code wrongly assumed index of tab bar buttons is fixed.
However tab buttons are simply a list and not a dictionary,
so index changes on any list update.
Use simply a binding to get correct tab button index.
This amends ba883b698bc98819de114f1af6f9efc70662ee19.
Pick-to: 6.10 6.9
Fixes: QTBUG-139461
Change-Id: I95a30d12ccc954f92895b76cea9948494189b8b1
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
|
|
|
|
| |
Task-number: QTBUG-140629
Change-Id: Iab2d22dba0ff8728786f3554bb537808735782cd
Reviewed-by: Topi Reiniö <topi.reinio@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
Add the missing implementation of
ContentBrowserClient::GetUserAgentBasedOnPolicy().
Pick-to: 6.10
Task-number: QTBUG-140444
Change-Id: I0c4e1aa24690dc6ba4c524b97ce7e723b2933f42
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We use CorsURLLoader since the 124-based Chromium. This performs a
safety check on calling CorsURLLoader::OnReceiveRedirect(), since
fetch() requests have more strict rules when accessing cross origin
resources.
This patch extends our dummy response with the Allow-Origin header
(only in case of redirects), so the request interceptor API users
won't hit this wall.
Test case implemented by: Benjamin Terrier
Task-number: QTBUG-140889
Change-Id: I7025fb69b5ac9b8763d61cb2bf0880dcc20721cf
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
|
|
|
|
|
|
|
| |
[ChangeLog][QtWebEngineCore] Added HTML inputmode global attribute
support
Fixes: QTBUG-141573
Change-Id: I40bdbb39b89fc9dc1a5d7a76a6210ec8c2f48372
Reviewed-by: Moss Heim <moss.heim@qt.io>
|
| |
|
|
|
| |
Change-Id: Ic0ab820f0d4b5f096725a27a7542e3240c052420
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, if dma_buf was not supported or allocating a GBM buffer
object failed, we tried to fall back to a Vulkan texture, assuming the
failure was due to GBM being disabled. However, this fallback would
also fail because a Vulkan texture could not be generated, resulting
in the confusing warning:
"Backend texture is not a Vulkan texture."
This change ensures that the warning is only issued if Chromium actually
generated the texture using Vulkan, avoiding false fallback warnings.
Pick-to: 6.8 6.10
Change-Id: I8866120e6641a1dce846b26f707dc04b489893a7
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
Reviewed-by: Moss Heim <moss.heim@qt.io>
|
| |
|
|
|
|
|
|
| |
Pick-to: 6.10
Fixes: QTBUG-131546
Change-Id: If4a7a0ac0dafe1dc827667579a8d892a8e5162fe
Reviewed-by: Moss Heim <moss.heim@qt.io>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
|
|
|
| |
Change-Id: Ief73cdf55a64d38395761933937be2e2f5fb9493
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Single-process mode doesn’t allow the use of multiple profiles.
Qt WebEngine creates an off-the-record (OTR) profile by default, but
simplebrowser then attempts to create a non-OTR profile for browsing.
Creating a second profile results in a fatal error.
Detect single-process mode, and if it is enabled, make the first
window use the OTR profile. This allows the browser to test
single-process issues without crashing on start.
Change-Id: I1f9d7f151054cc4f1bd27f59924032dc4502b646
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
|
|
|
| |
Change-Id: I47b403c7bd8f5cba9a4bb84349df8b19546544d7
Reviewed-by: Qt Submodule Update Bot <qt_submodule_update_bot@qt-project.org>
|
| |
|
|
|
|
|
|
|
| |
Fix warning from qdoc, fix capitalization issues so links do work now.
Pick-to: 6.10
Change-Id: Iafcf63e47bdcc4192059f19fcbf6fbee892482d8
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Qml type registration complains about "...nor a default-
and copy-constructible Q_GADGET..."
Therefore change to be value type, add default constructor.
This amends 6f4315175d4c7846c0591954ed03b14d405c9a90.
Pick-to: 6.10
Fixes: QTBUG-141112
Change-Id: Ib230e3766bac2451d58da903ad1c1d44e5519862
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Go through all foreign registered types and
cleanup the code.
Divide file into two sections:
* qml object types
* qml value type
Use proper QML_VALUE_TYPE macro for registration,
Add CREATE_DERIVED_FREIGN_NAMESPACE macro.
Remove QML_UNCREATABLE as all value types should
be default constructable.
Note Fixes for QWebEngineDesktopMediaRequest are done
in separete commit.
Pick-to: 6.10
Change-Id: I0dfbcffc28d58c7cf46b7b7805e4ff0623f17f42
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
|
|
|
|
|
|
|
| |
'name' instead of 'description'.
Caught via warning from qdoc.
Pick-to: 6.10
Change-Id: I7cc65bc6b279c395759a4c4a12ea23620ccc9d8b
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
|
| |
|
|
|
|
|
|
|
| |
It seems that children property was overlooked.
Add it so it is posible to crawl the frame tree.
Pick-to: 6.10
Change-Id: Ie4e13ccbc695a4db3782ce2c993c74ebb3d1cc9a
Reviewed-by: Moss Heim <moss.heim@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QWebEngineFrame class includes QJsValue in its api, however
to make it work it would require instance of Qml engine.
In also means that using qwebenigneframe requires Qml module.
Move the methods/logic to new class qquickwebengineframe,
however keep the already added SMF and default constructor.
Deprecate broken usage of functions taking QJsValue.
This amends 3ee3548e4c663402848db3b1336bf56e7c6d327e.
Task-number: QTBUG-139710
Pick-to: 6.10
Change-Id: Ia45a52e9d8759f6a4641f8a121e8e05cd60c2eaf
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Reviewed-by: Moss Heim <moss.heim@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
|
| |
|
|
|
|
|
|
|
|
|
| |
It seems that using qjsvalue in core make no so much
sense as it needs qml engine.
Remove the header so user app does not have direct qml dependency.
Pick-to: 6.10
Change-Id: Icdc5ace44488904151f2ef0b1d0db097f036a30b
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|