summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Enable Windows sandboxAllan Sandfeld Jensen2019-12-1910-15/+131
| | | | | | | | | | | | | | | | | Enable sandboxing on Windows. Enable heterogeneous sandbox symbol resolution and statically link the sandboxing code into the helper process. This means we have two copies of the sandboxing code, one statically linked in the executable and one in the shared library. Since they are not exported they don't conflict, but we need to take to initialize the right version in the helper process binary, and pass its sandbox interface to shared library using it. For sandbox debug output, we also need to initialize the second copy of the commandlineparser and logging system. Fixes: QTBUG-51170 Change-Id: I8f503c8d6b40674465f32772ef906817dad2b449 Reviewed-by: Kirill Burtsev <kirill.burtsev@qt.io>
* Update chromiumAllan Sandfeld Jensen2019-12-181-0/+0
| | | | | | | | | | Submodule src/3rdparty dd8389c5..325f3b07: > Disable dumb code > Fix 32bit sandboxing on Windows > Merge remote-tracking branch 'origin/upstream-master' into 77-based Change-Id: Ibae8b8269a41eb3d832a706151c45860230980b2 Reviewed-by: Michael Brüning <michael.bruning@qt.io>
* Fix Q(Quick)WebEngineDownloadItem::setDownloadDirectory()Tamas Zakor2019-12-185-14/+29
| | | | | | | | | | | | | | | | | | Keep the custom file name if the calling order of setDownloadDirectory() and setDownloadFileName() changes. Also do not emit patchChanged signal twice if setDownloadDirectory() changes the uniquifier of the file name. Add TempDir for qml auto tests what uses QTemporaryDir() to create temporary directory for downloads. See https://cgit.kde.org/messagelib.git/commit/?id=2c113dcb155b11bf2c0af3c85544962485784b26 for details. Fixes: QTBUG-80566 Change-Id: Ia76f263558eaf55cb297700407948523788c6229 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Add entitlements to QtWebEngineProcess.appMichael Brüning2019-12-171-0/+12
| | | | | | | | | | | | | | | | | Adds entitlements needed by the QtWebEngineProcess.app bundle when running with the hardened runtime. To use these entitlements when deploying an application with the hardened runtime enabled or notarizing it. To use it, deploy and sign the application using macdeployqt, then re-sign it using the additional entitlements that are contained in this patch. Coming version of macdeployqt may do this automatically when the hardened runtime is enabled. Task-number: QTBUG-77442 Change-Id: I7fde358725cf2d490f5e644934bf6466c2b4e1cb Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Fix typo of gn parameter for clang-clYuhang Zhao2019-12-151-1/+1
| | | | | | | | | When I try to compile Qt WebEngine through clang-cl + lld-link, gn complaints about the unknown parameter "use_ldd" and suggest to use "use_lld" instead. Change-Id: Id996699616db4eb0c67feaa29749a070465fc44c Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Fix ResourceBundle::GetNativeImageNamedJüri Valdmann2019-12-121-3/+1
| | | | | | | | | | Follow Chromium's aura, android, windows, and fuchsia implementations of GetNativeImageNamed by forwarding the call to GetImageNamed. Fixes DCHECK when enabling TouchEmulator in devtools. Change-Id: If5fdc30293bc18843c85d932f75f7cb2c70e5815 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Fix touch flinging in viz modeJüri Valdmann2019-12-122-0/+6
| | | | | | | | | | | FlingScheduler, in viz mode, is not able to progress the animation unless it has access to our ui::Compositor in RHWVQt for observing OnAnimationStep. Add a GetCompositor virtual method to RHWV and override in RHWVQt. Fixes: QTBUG-80089 Change-Id: I4f52a83d29f5ae4c7c9e8cc4908384d1c7e81a82 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Update ChromiumJüri Valdmann2019-12-121-0/+0
| | | | | | | | | | | | | | This pulls in the following changes: c7bb975f833 Fix manifests for extensions 88050fc712d Fix rebuilding of about resources every time 4a0ac259d12 third_party quiche: add missing include for iostate 819bf79725a [Backport] Set priority for requests whose load is emulated db19ca9c53c Fix FlingScheduler in viz mode dd8389c580c FIXUP: Fix manifests for extensions Change-Id: I7299c2e3c75840e943173191e28f4f1a1d42b087 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* Merge remote-tracking branch 'origin/5.14.0' into 5.14Allan Sandfeld Jensen2019-12-0418-42/+34
|\ | | | | | | Change-Id: I4f73d4b11bee795185d4eaae718d4cfdb3112100
| * Update Widevine path for Linux support of CDM videosv5.14.0-rc1Allan Sandfeld Jensen2019-11-301-1/+6
| | | | | | | | | | | | | | Fixes regression with Amazon Prime and Netflix. Change-Id: Ic96b4fa94fd06bfb9f7d75ca36e7eeddcda81218 Reviewed-by: Michael Brüning <michael.bruning@qt.io>
| * Fix 'setDownloadDirectory' for download item on 'SavePage' actionKirill Burtsev2019-11-2910-16/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| * Update find request id when a new search interrupts an ongoing searchPeter Varga2019-11-281-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| * Update ChromiumMichal Klocek2019-11-281-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| * Fix renderProcessTerminated signalJüri Valdmann2019-11-283-21/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| * Fix pepper flash plugin permissionTamas Zakor2019-11-281-1/+2
| | | | | | | | | | | | | | 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>
| * [macOS] Update widevine search paths to new Chrome bundle layoutMichael Brüning2019-11-281-2/+2
| | | | | | | | | | | | | | | | | | 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>
| * Update ChormiumMichal Klocek2019-11-281-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| * Update ChromiumMichal Klocek2019-11-271-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| * Merge "Merge remote-tracking branch 'origin/5.14' into 5.14.0"Frederik Gladhorn2019-11-227-99/+45
| |\
| * | Re-enable X11 WebRTC support for desktop sharingAllan Sandfeld Jensen2019-11-222-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | | Fix regression in alt attribute of copied image urlsAllan Sandfeld Jensen2019-11-304-14/+58
| | | | | | | | | | | | | | | | | | | | | | | | The linkText hasn't had the alt attribute for a long time, so instead add direct support for contextual title and alt text. Change-Id: I88e1c43374d855da7fb0d1ca42c0eb474012f0f2 Reviewed-by: Kirill Burtsev <kirill.burtsev@qt.io>
* | | Support accept attribute of file inputSzabolcs David2019-11-294-7/+57
| |/ |/| | | | | | | | | | | | | | | Set name filters of QFileDialog and QML FileDialog to avoid presenting all file types. Task-number: QTBUG-76564 Change-Id: I321214a30bc7e875ad132b015c63282f4eb482bf Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
* | Doc: Fix documentation warningsTopi Reinio2019-11-202-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | Update ChromiumJüri Valdmann2019-11-191-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | Merge remote-tracking branch 'origin/5.13' into 5.14Allan Sandfeld Jensen2019-11-145-97/+43
|\ \ | |/ |/| | | Change-Id: Id70f0288cb1f2df758c9fd21f02a5c037594b25c
| * Fix compilation on CI5.13Michal Klocek2019-11-131-0/+1
| | | | | | | | | | | | | | | | Add include based on error log from CI. Task-number: QTBUG-79930 Change-Id: Id74615182376c4bd4dd506239c9c2dbda75292c2 Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
| * Doc: Add missing section title to list of featuresLeena Miettinen2019-11-111-1/+2
| | | | | | | | | | Change-Id: Ic4951c1b033306dab51e99c9dfca9f8381bb85e5 Reviewed-by: Michal Klocek <michal.klocek@qt.io>
| * Update ChromiumAllan Sandfeld Jensen2019-11-111-0/+0
| | | | | | | | | | | | | | | | | | 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>
| * Redo scale handling of pdf when printingMichal Klocek2019-10-313-96/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | Code-style cleanup in src/core/netAllan Sandfeld Jensen2019-11-1325-161/+168
| | | | | | | | | | | | | | Picking suggested changes for a clang-format run. Change-Id: I3539dee65f153257015af4a8670312e74980a9e4 Reviewed-by: Michael Brüning <michael.bruning@qt.io>
* | Doc: Update required Windows 10 SDK version to 10.0.18362Leena Miettinen2019-11-111-2/+2
| | | | | | | | | | Change-Id: Iff9de7663918999eebf8dd55789782f2a12f7111 Reviewed-by: Michal Klocek <michal.klocek@qt.io>
* | Store favicon URL when serializing QWebEngineHistoryDmitriy Kuminov2019-11-081-6/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* | Disable robustness againAllan Sandfeld Jensen2019-11-081-1/+1
| | | | | | | | | | | | | | | | | | 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>
* | Deprecate QWebEngineDownloadItem path API properlyTamas Zakor2019-11-051-2/+6
| | | | | | | | | | | | | | | | 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>
* | Code-style cleanup in src/core/extensionsAllan Sandfeld Jensen2019-11-048-106/+73
| | | | | | | | | | | | | | Picking suggested changes for a clang-format run. Change-Id: I1a803b0c0bbf305b3e0861fa42b47ee404b4b255 Reviewed-by: Michael Brüning <michael.bruning@qt.io>
* | Merge branch '5.13' into 5.14Allan Sandfeld Jensen2019-10-3013-53/+98
|\| | | | | | | Change-Id: I6ab2e949cb2fa3b2db55a1654d42667db6257eab
| * Merge remote-tracking branch 'origin/5.13.2' into 5.13Allan Sandfeld Jensen2019-10-2814-52/+98
| |\ | | | | | | | | | Change-Id: I5c95819f139bb0995475324bd33dab478802db59
| | * Track request interceptor destroy and update profile io data accordinglyKirill Burtsev2019-10-231-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| | * Update ChromiumAllan Sandfeld Jensen2019-10-232-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| | * Activate extensions on Linux for GCC version 5.3.1 as wellMichael Bruning2019-10-181-5/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| | * Update ChromiumAllan Sandfeld Jensen2019-10-171-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| | * Fix getDisplayMedia crashJüri Valdmann2019-10-171-35/+41
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| | * Disable explicitly glibMichal Klocek2019-10-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | 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>
| | * Update ChromiumAllan Sandfeld Jensen2019-10-151-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| | * Add workaround for broken rendering on embeddedMichal Klocek2019-10-141-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| | * Merge "Fix accessiblity events for combo-boxes"Allan Jensen2019-10-112-0/+20
| | |\
| | | * Fix accessiblity events for combo-boxesAllan Jensen2019-10-112-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| | * | Merge 5.13 into 5.13.2Frederik Gladhorn2019-10-111-0/+0
| | |\ \ | | | |/ | | |/| | | | | Change-Id: Ib246d7c44628611a35ca99ea8e5504288c63f4c1
| | * | FIXUP: Fix page and profile interceptors initializationMichal Klocek2019-10-102-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
| | * | Fix life cycle issue of QWebEngineUrlRequestInterceptorMichal Klocek2019-10-104-9/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since 5e92adf intercept() is called on ui thread, however this patch does not consider deletion of interceptor while io thread still process the request and for examples checks interceptor's deprecated property. Fix it. Note this only fixes issue for interceptors which are not deprecated therefore run on ui thread. Change-Id: I5d5909065563e57a0cacb81fd04271b3f88596de Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-18 20:29:21 +0000