| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: I134876aa68bd42356c0b897a5d7d5881f27724a4
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
|
|
|
|
|
|
|
|
| |
The max was bumbed from 11 to 256, now document it.
Task-number: QTBUG-69904
Change-Id: I6cbf64afe3409c4722d7a903d833124880b32bc0
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
|
|
|
|
|
|
|
|
| |
This pulls in the following changes:
* 708511 Fix hunspell::NodeReader::affix_id_for_leaf bounds check
Change-Id: I54a3775c171361f227a27bfd3846ab4f5a78e76c
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This pulls in the following changes:
* 084a80 [Backport] Security Bug 831117 2/2
* f78390 [Backport] Security Bug 831117 1/2
* d739b9 [Backport] Security Bug 683418
* cf51b5 [Backport] Security Bug 840695
* 009019 [Backport] Security Bug 838886
* 424911 [Backport] CVE-2018-6158
* 6d5f60 Fix compilation issues in introduced previous commits
* a6e2ca [Backport] Security fix for Chromium bug 860721
* 3e6d0c [Backport] Security fix for Chromium bug 839197
* f4115a [Backport] additional patch for security fix for Chromium bug 839197
Task-number: QTBUG-69663
Change-Id: I6ad8509efb210972b753d8763e02cc31e90e0f8a
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This pulls in the following changes :
* 827405 [Backport] Security fix for Chromium bug 854887
* e79b92 [Backport] Security fix for Chromium bug 861571
* d845af [Backport] CVE-2018-6161
* 3cdf31 [Backport] CVE-2018-6159
* 625870 [Backport] CVE-2018-6162
* 2b111a [Backport] CVE-2018-6164
* eb5360 [Backport] blink: disable XML catalogs at runtime
* 273272 Bump maximum number of custom isolated world ids
* 8f53e0 [Backport] CVE-2018-6167
* 07c34e [Backport] CVE-2018-6172 CVE-2018-6163
* 5d8596 [Backport] CVE-2018-6165
* e8b9ae [Backport] CVE-2018-6177 CVE-2018-6168
* 0cce34 [Backport] CVE-2018-4117
Task-number: QTBUG-69663
Change-Id: Ied119f9d0b28ccba4954c087ab7bcf129969d52a
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
--enable-webgl-software-rendering is supposed to be used together
with mesa llvmpipe / opengl32sw.dll. However, Chromium did still use
the built-in GPU blacklist to disable features based on the hardware
GPU driver.
Avoid this by always passing --ignore-gpu-blacklist for this mode.
Task-number: QTBUG-69236
Change-Id: I430d101f6eac64478585de54f705e76859c80597
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit pulls in security patches:
* CVE-2018-6150
* CVE-2018-6152
* CVE-2018-6175
* CVE-2018-6155
Task-number: QTBUG-69663
Change-Id: If70e7817f4f9aa1fa482559b734085e6cdff89ed
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
|
|
|
|
|
|
|
| |
Not needed and triggers race condition.
Task-number: QTBUG-69007
Change-Id: Id57ba527387e5dbe44a8dd6c5a49e7278403ce64
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changes:
2d61f0a269 Work around MSVC2017 optimizer bug when printing a page usind Pdfium
6d6103fe51 [Backport] flush to zero tiny radii
edf63ed29d [Backport] use double to compute root to avoid overflow
7777b6ac95 [Backport] Generate GL errors more strictly in StrictIdHandler.
0c00f4a924 [Backport] Validate all incoming WebGLObjects.
a6a96845cc [Backport] Prevent potential buffer overflow in UlpfecReceiver
a3d55fb8e4 [Backport] Check number of nalus in packet before checking nalu types.
Change-Id: Icd501a956ce396a38098272848bc25065ad92748
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
|
|
|
|
|
| |
Change-Id: I74f6a607d96733fa379526be40c6a13c31203d4e
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
|
|
|
|
|
|
|
|
|
|
|
| |
IODevice::close and therefore aboutToClose is called by io thread,
connecting it to deleteLater will register deferred delete
on event loop of IODevice instance, which is on ui thread.
This could be racy since deletion on ui thread can happen before job
is done.
Change-Id: I895e6a71649ba65944d069f254d119cc60aada6c
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When an HTML select box was clicked inside of a QWebEngineView and
the parent QWebEngineView window was moved using the mouse
(via window decoration toolbar for example) the popup window
would stay around instead of being closed.
This happened because of the usage of the Qt:Tool window flag for the
popup window, which implies a tool that floats near its parent window.
The fix is threefold:
1) Use Qt::Popup instead, similarly to how QMenu does it.
Whenever the parent window is moved, the popup will now get a
CloseEvent.
2) Handle the CloseEvent by telling Chromium to close and destroy
the popup.
3) On Windows the OS might send mouse move events to the popup RWHVQD
instance after its parent QWebEngineView, RWHVQD,
QWebEnginePagePrivate (client adapter) is destroyed. We need to
guard the mouse forwarding code not to access the client adapter
if it has already been destroyed.
The second point is done by telling Chromium that its popup lost focus
which it interprets as a sign to hide it, and automatically destroy
it. This will destroy the underlying RWHVQtDelegateWidget and
RWHVQt instances.
Task-number: QTBUG-59891
Change-Id: I47f94a93c495a6caa5de92a6022eaca154994eda
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
|
|
|
|
|
| |
Task-number: QTBUG-69605
Change-Id: I863db484ff2bcf558585f75c73963097fb43148a
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Include following patches:
c020786f57 Fix compilation failure in time_win.cc
eea22d3cac [Backport] media: Increase DecoderBuffer::kPaddingSize to 64
91d24cdd6f Reduce severity level of messages when kDisableGpu switch is
used
298fb05460 Fix --single-process --disable-gpu combination not to hit
asserts
db81dc68a8 Remove incomplete logic to detect AMD K2 CPU's
b11fd882e8 Do not write <protocol>.json to source directory
Change-Id: I4e3c0c2f3908f358b43ae4af8baebc2012c9830b
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
|
|
|
|
| |
The documentation says we require 4.7 or later but actually already since the
5.10.0 release our qmake config has been checking for version 5 or later.
Task-number: QTBUG-69535
Change-Id: Ia2f74b35570a9ba6fd1423b9507fe636d850db76
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
|
|
|
|
|
|
|
|
| |
Adds note for QWebEnginePage::print(...) function.
Change-Id: I52ec78ccfc5c4eeb98ee69f9aaab01b380f97a81
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: Szabolcs David <davidsz@inf.u-szeged.hu>
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The empty URL is used both for representing a missing origin (browser-initiated
navigation request) and a unique/opaque origin. This is problematic since the
security implications are very different in these two cases: browser-initiated
requests usually should have high security clearance, while requests from unique
origins should be restricted.
Task-number: QTBUG-69372
Change-Id: Iff73fd1c9a29f1c5c281a8945536333081ff2d6b
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
- Use OpenURL on the devtools WebContents.
- Guard against self-destruction (otherwise quicknanobrowser crashes).
- Change quicknanobrowser to open links in new tabs.
Task-number: QTBUG-69359
Change-Id: I4db379731c6fa855124d38c5066b0aad622861d2
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
DragTargetDragEnter expects the 'int key_modifiers' parameter to have values
from the enum blink::WebInputEvent::Modifiers and not ui::EventFlags.
Also, contrary to the name, mouse modifiers are also expected.
Task-number: QTBUG-69231
Change-Id: I2369609775243fded563dde7675c4bc2dfc81021
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
|
|
|
|
|
|
| |
Task-number: QTBUG-69231
Change-Id: I35b503dae7e2d90b26b6e61a4c7c260e45df2b62
Reviewed-by: Filipe Azevedo <filipe.azevedo@kdab.com>
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
|
|
|
|
|
|
|
|
|
| |
Because windows.pri is included from a replace function gnArgs,
fatal does not work:
src/core/config/windows.pri:60: 'fatal' is not a recognized test function.
Change-Id: Ib831e1ffa7e8e345477692d453bbcc568864b98c
Reviewed-by: Andy Shaw <andy.shaw@qt.io>
|
|
|
|
|
|
|
|
| |
This should enable excluding such snippets from
documentation in some cases.
Change-Id: I46854412546e3774889e09831254828d18362f29
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
|
|
|
|
|
| |
Change-Id: I7e03d6e3347ee9b81a7414574098827b5773b7b4
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
| |
Regenerate the tree when different nodes are clipped.
Task-number: QTBUG-68699
Change-Id: Ib59a0b92463c47f89b7a6c662abe532fb4130c3c
Reviewed-by: Florian Bruhin <qt-project.org@the-compiler.org>
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
|
| |
Task-number: QTBUG-68933
Change-Id: I395157a9931a0e0789b3791cc9b4d55dbcf8a4c2
Reviewed-by: Topi Reiniö <topi.reinio@qt.io>
|
|\
| |
| |
| | |
Change-Id: Ia68ebcab9d04914cf65bff3548396f081485ce6a
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Pulls in following commits:
* bad02200 [Backport] CVE-2018-6149
* 8cc9828a Workaround long path issue on Window
* b42eb615 [Backport] gpu: Address piman's nits from crrev.com/c/969639
Change-Id: I3077df475503db990988ff0ab42724d11341db25
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Pulls in security patches:
* CVE-2018-6148
* Security Bug 835371
Change-Id: I00ac63f834082217b7290c90deb261dae0c99746
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|/
|
|
|
|
|
|
| |
Use the GLContext to find address for eglGetProcAddress symbol, if it's
not found with dlopen.
Change-Id: I3f5330c21ecc9b66e5e376d50d3fc6965b227f85
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
|
|
|
|
|
|
|
|
| |
We could end up dropping visible blocks during scrolling if only one
pixel line was left and the viewport got rounding one line too small.
Task-number: QTBUG-68699
Change-Id: I1ab646f23d8dd4911b32d02df68c80d6a8d78651
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
Pulls in following security patches:
* Security Bug 836511
* Security Bug 835184
* Security Bug 823864
Change-Id: I479a12be518a288db4aed88447d5a8cc33f41822
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
Pulls in following security patches:
* Security Bug 826946
* Security Bug 826193
* Security Bug 825524
* CVE-2018-6145
Change-Id: Iae4ada1157df1793cb1c5a06be55835d696df3d5
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
Pulls in following security patches:
* CVE-2018-6144
* CVE-2018-6143
* CVE-2018-6142
* CVE-2018-6137
Change-Id: I878529f2061e3da2397756ac5adf8ee0139e7602
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Do not include <QOpenGLContext> with gl_bindings.h since
this will eventually include gl and gles heders into same
compilation unit.
Confilicting headers:
third_party/khronos/GLES3/gl32.h
third_party/mesa/src/include/GL/gl.h
Change-Id: I0450a4084011ead4bfa80d68aeea3f5859df4c94
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
Pulls in following security patches:
* CVE-2018-6135
* CVE-2018-6136
* CVE-2018-6134
* CVE-2018-6133
Change-Id: Icaa7bf00f77e1d7da75518e07118018f674646ab
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
Pulls in following security patches:
* CVE-2018-6132
* CVE-2018-6130
* CVE-2018-6129
* CVE-2018-6127
Change-Id: I5a1923d9d95ce61a9fc6dff58ccb79498b8e5ecb
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Old behavior:
- Hotspot always chosen according to 2x devicePixelRatio.
- Image always chosen according to 1x devicePixelRatio.
New behavior:
- Use actual devicePixelRatio.
Task-number: QTBUG-68376
Change-Id: I6eef12a7dcf7fde7f8f488d9f2cba99f21e73cc2
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Pulls in following changes:
* 37866ea Fix race condition on gpu thread initialization
* 1fc1c33 [Backport] CVE-2018-6120
* d8c9a86 [Backport] CVE-2018-6123
* 9a297a3 [Backport] CVE-2018-6124
* 0979afc [Backport] CVE-2018-6126
Change-Id: Ia8995000d8a5db0e3b23f445ab2d750e51609d23
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
| |
Avoid including texture_manager.h that pulls in conflicting GL headers.
Task-number: QTBUG-68244
Change-Id: I3174b00498e7a4772d2bb302d886071ba3bd2a64
Reviewed-by: Viktor Engelmann <viktor.engelmann@qt.io>
|
|
|
|
|
|
|
|
| |
Calling triggerAction for a context-menu-specific action (like
DownloadLinkToDisk), when no context menu exists, will crash.
Change-Id: Ife647b7a7d8ab1a0d9dcb7d3566be130516e6e63
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
Qt WebEngine requires a newer freetype version then Qt Gui. Also,
even if we fall back to 'Qt' freetype in Qt Gui doesn't mean
that this version is shared with Qt WebEngine ... so it's best
to completely detangle these.
Task-number: QTBUG-68439
Change-Id: I081a23fe3e573d717a659e9bccebb14d68e97392
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is an improvement of:
bab4abab Keep settings synchronized when RVH swaps
Updating settings during RVH swap is flaky because it happens after
the load start of RenderFrame thus it is not guaranteed the
ViewMsg_UpdateWebPreferences message is received by the render process
before the load finishes. This means that the setting might not be applied
on the current page if it was set during the navigation.
The new RVH is created at the very beginning of the navigation, so access
it via the pending or speculative main frame of the page thereby make it
possible to update its settings before the load of RenderFrame starts.
Task-number: QTBUG-66656
Task-number: QTBUG-68424
Change-Id: I4fbba597579551bb3329936ccd7b357cf8daa4ea
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
YUV to RGB color conversion was not working, because the provided
ColorSpace object was invalid.
According to gl_renderer.cc, invalid color spaces should be treated
as REC709.
Task-number: QTBUG-68174
Change-Id: I1ad3b74ced4734e048256c075c953e9218ca6b6c
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
| |
Task-number: QTBUG-68364
Change-Id: Ib2079ccd211b537725fd0992e069c41df01c5e7b
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
|
|
|
|
|
|
|
|
| |
Some actions, like Copy, are never updated and therefore need to be always
enabled.
Task-number: QTBUG-68354
Change-Id: I6827ee719ddc55cad3e4359379d1f2980f4b9618
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
|
|
|
|
|
|
|
|
| |
Reverts incorrect change to src/3rdparty in bd3687d2c5 and adds
96f354df27 Fix build with GCC 8.1.0
Change-Id: I6d4334598beb719aca0dabc96060630ea34015e9
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
| |
This was moved to later, but rebasing the patch lost this line.
Change-Id: I5a8f098519bb4e0ab4dcd6a5855a4c8576a46753
Reviewed-by: Viktor Engelmann <viktor.engelmann@qt.io>
|
|
|
|
|
|
|
|
|
| |
Otherwise Chromium will pick the last added, meaning we will use the
wrong one.
Task-number: QTBUG-64071
Change-Id: Id5c939b6a5c70643ed047625c0cbb152dd8c7169
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
|
|
|
|
|
|
| |
There can be more than one RenderViewHost assigned to a single
WebContents. This is the case when starting a page load results changing
processes. When applying settings during the load it updates only the old
RVH. This fix applies the settings to the new RVH too after the swap.
Task-number: QTBUG-66656
Change-Id: I833415b2a34f58e2a9a18c209a025c82b73aa65a
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Turns out JavaScript's JSON.stringify is not guaranteed to produce valid UTF-16
strings. It is possible in JavaScript to produce string objects which contain
invalid code units (unmatched surrogate pairs) and JSON.stringify will simply
copy this data to it's output. However, such a string cannot be losslessly
converted to UTF-8 and this leads to fun errors in WebChannelIPCTransport.
This patch
- Adds a test for the scenario above.
- Changes WebChannelIPCTransport to replace these invalid code units with the
Unicode replacement character U+FFFD.
- Changes WebChannelIPCTransportHost to validate the data it gets from the
renderer. Not validating the data defeats the whole point of Chromium's
fancy multi-process architecture: the renderer is not to be trusted.
- Changes WebChannelIPCTransport to throw JavaScript exceptions for various
errors (missing argument, wrong type, invalid JSON). Seems like the polite
thing to do.
Task-number: QTBUG-61969
Change-Id: I83275a0eaed77109dc458b80e27217108dde9f7b
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|