| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: If15b7d4110a9d8deb10c15363e63043d83ef2a35
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
|
|
|
|
|
|
|
| |
Fixes regression with Amazon Prime and Netflix.
Change-Id: Ic96b4fa94fd06bfb9f7d75ca36e7eeddcda81218
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Chromium's DownloadManager doesn't create its download items before
path for saving page is confirmed. So assert inside updateDownloadPath
was not correct. Moreover, the name is confusing because it's not really
updating anything. Remove it and use ProfileAdapterClient::DownloadInfo
timestamp to determine updated filename after directory change.
Ammends recent new api for changing download directory 0884fab3b1.
Fixes: QTBUG-80372
Change-Id: If9efb52979deb3cf21fc4e12989173c85e04e090
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>
|
|
|
|
|
| |
Change-Id: Ifbcf7f70ddbed7768e5e7b7231661a69d6d9f1a1
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
| |
Amends fc0dbde734 timeouts adjust for slower CI
Change-Id: I77bacfb973cfe8e2c259a31d58f439ffcae7b87f
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the new test became flaky it might happen because the first text
search finished before the second findText() call. This is very
unlikely, but in this case the test should be modified to not to check
if the first find failed. The point is to check we get the correct
amount of signals and the second search doesn't assert.
If the callbacks will be removed in Qt6, it should be re-considered to
remove the "unfinished find" workaround and trigger the first successful
findTextFinished() signal even if it happens in the middle of another
search.
Fixes: QTBUG-80086
Change-Id: I9c1ce20fc43fd81e8af784385a00ac2e7f7603b7
Reviewed-by: Kirill Burtsev <kirill.burtsev@qt.io>
|
|
|
|
|
|
|
|
| |
Amends import fix f4fa4d3d34 after api review
Task-number: QTBUG-80249
Change-Id: If4b2cb65e94de8c648b2c234490a6d6325615ba6
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Pulls in following changes:
* 7d2876b9557 Fix url_utils for QtWebEngine
* bfea09e6e17 FIXUP: Add net::URLRequest::first_party_url()
* 0d4406b3688 [Backport] Security bug 961614 1/8
* b1a56dab182 [Backport] Security bug 961614 2/8
* b9718cd4aa0 [Backport] Security bug 961614 3/8
* 821f375089e [Backport] Security bug 961614 4/8
* ee18fd483a7 [Backport] Security bug 961614 5/8
* 105f1e578c3 [Backport] Security bug 961614 6/8
* 09050e17c6a [Backport] Security bug 961614 7/8
* 634aff72b47 [Backport] Security bug 961614 8/8
* c5eb4cfff7f [Backport] Security bug 775511
* 120ccb55b5c [Backport] Security bug 1015945
* 939daf833ff [Backport] Security bug 955191
Task-number: QTBUG-79465
Change-Id: Ic9585b656477fae364ab17631db7487e8a00d46c
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the adaptations for Chromium 76, RenderWidgetHostViewQt was changed to
become a RenderProcessHostObserver with the renderProcessTerminated signal being
emitted from the override of RenderProcessHostObserver::RenderProcessExited.
The problem with this can be seen by setting a breakpoint on the
RenderProcessGone override in RenderWidgetHostViewQt. We then get the trace:
QtWebEngineCore::RenderWidgetHostViewQt::RenderProcessGone
content::RenderWidgetHostImpl::RendererExited()
content::RenderViewHostImpl::RenderProcessExited
content::RenderProcessHostImpl::ProcessDied
ProcessDied iterates over all the observers and calls RenderProcessExited. Both
the RenderViewHostImpl and our RWHVQt are observers, but the RVHImpl comes
first. The RVHImpl then calls RendererExited, which calls our RenderProcessGone,
which does a 'delete this'. Now our RenderProcessExited override can never be
called because we have already deleted our observer.
Fix by moving the RenderProcessGone code to WebContentsDelegateQt and getting
the exit code from WebContents::GetCrashedErrorCode. Also add test.
Task-number: QTBUG-80085
Change-Id: I434744286df97a37b64722d7c15a1d4ee11c8af6
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
| |
Fixes: QTBUG-78280
Change-Id: Ic202314bb7935741791fa8c747e255b10dc7dc61
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
Reviewed-by: Florian Bruhin <qt-project.org@the-compiler.org>
|
|
|
|
|
|
|
|
|
| |
Re-enables using proprietary codecs used by many popular platforms
for streaming video.
Fixes: QTBUG-80352
Change-Id: Id1730576a98cfc4b23b523e61c1d8168414e3a48
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Pulls in following patchs:
* 77c86be6077 BASELINE: Update Chromium to 77.0.3865.129
* cbc9c4a3c8d Merge remote-tracking branch 'origin/upstream-master' into 77-based
* 6f690b4418f Merge "Merge remote-tracking branch 'origin/upstream-master' into 77-based" into 77-based
* d61464c1e69 Fix is_main_frame in intercept_navigation_throttle
* 41d6b0b2f16 [Backport] Secuirty bug 1014607
* e751f134d6b [Backport] Security bug 1016450
* 5b40e1d793e [Backport] Security bug 1018406
Task-number: QTBUG-79465
Change-Id: I0fd5c5bbdeb5d3478d9646540bca0550f0eb3819
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Pulls in following changes:
* 1d9d75d072e Fix '/Zc:twoPahse' unknown compiler option warning
* 55c0556c1ca [Backport] Security Bug 1003313
* d5f6e269885 [Backport] CVE-2019-13721
* c1fd5c47504 [Backport] Security bug 1011551
* e9b6a6d0cf9 [Backport] Security bug 1006544
* 8a477bb16f9 [Backport] Security bug 997401
* 6ed410d94fc [Backport] Security bug 995591
* ccde4d23e60 [Backport] Security bug 993266
* 8564d6c04aa [Backport] Security bug 989909
Task-number: QTBUG-79465
Change-Id: I54841d9116c65fdab62eba5199382686297e960a
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
|\ |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
This is the final down-merge of Qt 5.14 to the 5.14.0 branch.
Fixes: QTQAINFRA-3355
Change-Id: Ia084ee85539b6d2dfcb579ff5e7fa3256337fa1b
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Remove links to example files, as QDoc no longer treats them as linkable
targets.
Fix linking to WebEngineView.selectClientCertificate().
Fix missing parameter documentation in WebEngineView.tooltipRequested().
Fixes: QTBUG-79815
Change-Id: I9090d3cfb1b698a545ae54a7426bb0a4eef892e9
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This pulls in the following changes:
7e3ec623081 [Backport] Fix for CVE-2019-13720
59d24cbd63e Fix QRC cookies for tests with network-service
42c122dcb80 Fix Windows sandbox for heterogeneous executables
4d310ae5bc3 [Backport] CVE-2019-13700
d9cbe788437 [Backport] CVE-2019-13701
30dfb122e96 [Backport] CVE-2019-13704
51fdc9e9dc6 [Backport] CVE-2019-13706
9ea3feb658c [Backport] CVE-2019-13711 1/2
6ab99196115 [Backport] CVE-2019-13711 2/2
394da2e8dd7 [Backport] CVE-2019-15903
929d812ae1d [Backport] CVE-2019-13714
6c31ac36355 [Backport] CVE-2019-13715
bf4615cbfa1 [Backport] CVE-2019-13718
35fb44f1bdc [macOS] Fix build error with new deployment target
03e611b862a Revert "[Backport] CVE-2019-13701"
948c21d2163 Support GPU service on UI thread with viz
147452f856e Fix previous fix for new macOS deployment target
cf3564f25ee FIXUP: Support GPU service on UI thread with viz
040ccbbef2d Fix pdfium build on macOS
Task-number: QTBUG-79940
Change-Id: I6e3046b3b5d855cbfd8657dcaa816649938f73a5
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| | |\
| |/ /
| | |
| | | |
Change-Id: Id70f0288cb1f2df758c9fd21f02a5c037594b25c
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add include based on error log from CI.
Task-number: QTBUG-79930
Change-Id: Id74615182376c4bd4dd506239c9c2dbda75292c2
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: Ic4951c1b033306dab51e99c9dfca9f8381bb85e5
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Changes:
da37c1e0c517 [Backport] CVE-2019-13662
d6e5fc10e417 [Backport] Fix for CVE-2019-13720
Change-Id: Iea896b1cef9cc582654d0112408fc63539ee9a1a
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since 7f89bad our printer handling produces low quality
images, the reason for that is the we first render
with pdfium to bitmap which is fixed to twice size of pdf
document in points, then it is downscaled/upscaled by
qpainter. This issue is even more visible when print preview
is requested on hdpi screen.
Simplify the code and do the "scaling" already when rendering
bitmap with pdfium.
Task-number: QTBUG-75092
Fixes: QTBUG-78161
Change-Id: I616ad1f371e7d3457a04b0a254603ed235c387bc
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
With corresponding fixes in chromium, we should now again be able to
support WebRTC desktop sharing with X11.
Fixes: QTBUG-80055
Change-Id: If1ce50fe8e83d2c5086c6735d205bc4ca424746d
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
Picking suggested changes for a clang-format run.
Change-Id: I3539dee65f153257015af4a8670312e74980a9e4
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: Iff9de7663918999eebf8dd55789782f2a12f7111
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is to make QWebEngineHistoryItem::iconUrl of the deserialized
QWebEngineHistory object return the same URL it had when serializing. Otherwise
it's impossible to have favicons for URLs from the navigation history of a
restored browser session until these URLs are visited again
(so that Chromium refetches their favicons). These icons are usually needed much
earlier - e.g. when showing a popup with the navigation history and having an
icon URL allows to load it from a disk cache before visiting the page.
Fixes: QTBUG-78998
Change-Id: Ief2d089d52f301826e5c131d401cafd08952a8b5
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It again doesn't work and now causes extra problems, even on the
intended hardware in the intended use-case.
Change-Id: Ie915cb07bdbdfd1a5db83a8e565e43dfc74f042c
Fixes: QTBUG-78461
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Try importing JS modules from a setHtml page.
Fixes: QTBUG-77282
Change-Id: I925bd3239688117c380ed3ae404dcb9547d99cac
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The test now reports it would succeed with a longer timeout on loading.
This should be investigated later as the timeout is really out of line,
or what should be acceptable.
Task-number: QTBUG-79852
Fixes: QTBUG-79719
Change-Id: I60c1e6e0f7026b5ad61db2e22512dd45e1162e1c
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Expand many more timeouts as loading basic test cases can now take
many seconds.
Task-number: QTBUG-79290
Change-Id: I749fe50525919b24a4a3fcba905745b6d6648121
Reviewed-by: Kirill Burtsev <kirill.burtsev@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Implements suggestion from 5.14 API review:
- Replace QT_DEPRECATED with QT_DEPRECATED_SINCE and QT_DEPRECATED_VERSION_X
Change-Id: I4d0bf8a2b535c44b5749cbd3bbab7e305bd137c6
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Cleanup page between tests, increase load timeout and switch to QVERIFY_TRY
to be told of timeout overruns.
Fixes: QTBUG-79719
Change-Id: Ic246a5b0926c3e8b6c0f90f5ff21a33fa262c046
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
Picking suggested changes for a clang-format run.
Change-Id: I1a803b0c0bbf305b3e0861fa42b47ee404b4b255
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
|\ \
| |/
| |
| | |
Change-Id: I6ab2e949cb2fa3b2db55a1654d42667db6257eab
|
| |\
| | |
| | |
| | | |
Change-Id: I5c95819f139bb0995475324bd33dab478802db59
|
| | |
| | |
| | |
| | |
| | | |
Change-Id: I623b33e2b3c4bb6efd6cf9fd105266637dcb0e3b
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On destroy profile level interceptor is cleaned through QPointer
in ProfileAdapter but not in ProfileIOData where it is stored as
a raw pointer and used by NetworkDelegateQt.
Track 'destroyed' signal and clean it from ProfileIOData,
which resolves these issues after interceptor is deleted
without explicitly being reset in profile:
- for deprecated 'setRequestInterceptor': one of possible
access violation in NetworkDelegateQt::OnBeforeURLRequest
- for setUrlRequestInterceptor: sending URLRequestNotification
for every url request after interceptor is deleted
Fixes: QTBUG-79156
Change-Id: Ie2dd3f0909bc45748278c5f97c5c2701742591b5
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Changes:
b5d06a458283 [Backport] Security issue 946978 [1/2]
4f553e3a0c62 [Backport] Security issue 946978 [2/2]
32d77d99be3f [Backport] CVE-2019-13674
2a45953d844a [Backport] CVE-2019-13675
2708f4fe1f1a [Backport] Plumb initiating origin info to download stack.
1d21cbce407f [Backport] CVE-2019-13678/CVE-2019-13681
0da18c7f04e3 [Backport] Security issue 960354
4e50fd02436d [Backport] Security issue 973628
9e3becc64121 [Backport] Security issue 979373
729e9b30bbf2 [Backport] Security issue 981459
28150e5eb962 [Backport] Security issue 981597
843d70ac87de [Backport] Security issue 971904
Fixes: QTBUG-79193
Change-Id: Ic90455446f79500d5971a975e2a04344f65238ac
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This removes the special handling for the lower GCC versions that
we support on linux. This will make the extensions and the PDF viewer
available on the pre-built linux packages.
Change-Id: I7b79c82f8e2596e2401e05f81041d736486d1c7d
Fixes: QTBUG-76329
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Changes:
01b3f792f17b [Backport] CVE-2019-13659
d0e61ebba346 [Backport] CVE-2019-13694
9312eb97bf60 [Backport] Security issue 986727 [1/2]
66c739040bba [Backport] Security issue 986727 [2/2]
b1ce3367b489 [Backport] CVE-2019-13660
ade14af90b01 [Backport] CVE-2019-13633 [1/2]
5f5f67b3a1f5 [Backport] CVE-2019-13664
6ddab05a4c71 [Backport] Security issue 990234
e8ba421d30c9 [Backport] CVE-2019-13663 [2/2]
1f64c1f27840 [Backport] CVE-2019-13665
8635cf233cdf [Backport] CVE-2019-13668
691467ccbb87 [Backport] CVE-2019-13673
fe065266295e [Backport] Security issue 946351
e989f4cb8907 [Backport] Security issue 964938
6114514c9e76 [Backport] Security issue 974354 [1/2]
858447a76544 [Backport] Security issue 974354 [2/2]
3d7a96629b79 Convert asserts to logs and returns in the PpapiHost
a42666a17663 Apply workarounds to build extensions with gcc 5.3.1
18d4c6e82503 Revert "[Backport] CVE-2019-13668"
Task-number: QTBUG-79193
Change-Id: I2b70a4343fd37321e0c10e574e515e42930ada10
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The MEDIA_DISPLAY_VIDEO_CAPTURE stream type is handled incorrectly by
MediaCaptureDevicesDispatcher causing a crash when an unexpected type of media
device is returned to Chromium.
This patch only fixes the crash, screen sharing is nonetheless not properly
supported by WebEngine due to limitations of the public API which does not allow
selecting between screens, not to mention windows or tabs.
On Linux WebRTC's ScreenCapturer is not even built since it depends on use_x11
being set in GN.
Fixes: QTBUG-78016
Change-Id: I7fa49febaba1be94bdb6c31265dfc24ee809d635
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There some issue with running glib event message pump,
due to coming release just make sure glib is disabled.
Change-Id: Ibe7b89ddfbcd57dbb41cfbc5d6a8ad1c69be39cb
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Changes:
6a5dc3af3537 [Backport] Reintroduce glib message event loop 1/3
580ffe2cb750 [Backport] Reintroduce glib event loop 2/3
9ae8ddaeea11 Reintroduce glib event loop 3/3
1f07ca687b1a [Backport] CVE-2019-5870
00d9e1e3be09 [Backport] CVE-2019-5872
d627df149baa [Backport] CVE-2019-5875
2d9ed8b1aaa6 [Backport] CVE-2019-5876
bebd1df6d51d [Backport] CVE-2019-13691
1c7141ad185b [Backport] CVE-2019-13692
f0e6f7f8a392 [Backport] CVE-2019-13688
495b2ebcd9d3 [Backport] CVE-2019-13687
cc18c848e174 [Backport] CVE-2019-13693
b41d57627c00 [Backport] CVE-2019-13695
c88d2026cc60 [Backport] CVE-2019-13697
Task-number: QTBUG-79193
Change-Id: I1a318d573d5f95c8bad02e96ed5084a1a1ef7bf8
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On some boards we get wrong tile textures on the screen. It
looks like this is some sort of a race condition or a problem with gl
fencing. Add quick workaround by setting QTWEBENGINE_DISABLE_GPU_THREAD
env. variable to force no in-process-gpu-thread.
Change-Id: Ib397b04e039a279413c79277e25b77064b9b6854
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| | |
| | |
| | |
| | | |
Change-Id: Ic761ec9a79057f18ebea20ff2556eaac63d39d75
|
| | |
| | |
| | |
| | | |
Change-Id: Ideee5087290cf2a1d081261d832c8ceb11aeeae8
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The editable text-fields gets value-changed events from
Blink instead of the text-changed events we needed.
Change-Id: I688c06b644f333a3ba1ebd8831adbbbb7d49cbe7
Fixes: QTBUG-78206
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
|
| | |\ \
| | | |/
| | |/|
| | | | |
Change-Id: Ib246d7c44628611a35ca99ea8e5504288c63f4c1
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previous commit showed an issue when interceptors are set before
URLRequestContextGetterQt is created. The initial initialization was
done on updateStorageSettings() which only affected profile interceptor
initialization. Add explicit updateRequestInterceptor call
to have profile and page interceptors initialized. This fixes also
the issue of not set properly 'deprecated' flag.
Change-Id: I0dda9eff67a2d779f4c9693920077a5aac2d9122
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|