| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Use ozone glx instead of x11 glx.
Task-number: QTBUG-65682
Change-Id: I612ff7993812607a170a42c4fe72abd9913ef0c5
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
| |
Change-Id: I38a73bfd4dfaa930253f6d82eff940b4e03820c2
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|\
| |
| |
| | |
Change-Id: I864dabe43f1057024ef3560001c820d1734d96c0
|
| |
| |
| |
| |
| | |
Change-Id: I9a14af4efb092ab203e9364f0779fca781909a38
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: I488c70fc54dfed95d3b346735e63f5aa0c6f1a88
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is basically commit 363741cffb565dd6cfc2f95054c25a434b101dba
from 56-based, with the required modifications due to code changes.
Borrowing the original commit message:
ICU 59 changed the UChar type to be char16_t instead of uint16_t and
that causes a mismatch of types all over Chromium.
Unfortunately the upstream patches can not be used as Chromium only
got part way in https://codereview.chromium.org/2740673002, and
then gave up and simply patched their copy of ICU 59 to not change
that.
Task-number: QTBUG-65090
Change-Id: Icbe46fa33bf56fc3a5aedd5b6004fc029fa24930
Reviewed-by: Jimi Huotari <chiitoo@gentoo.org>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
GLSurfaceQtWGL does need PBuffer support to actually create a
surface. Make sure that the appropriate OpenGL extensions are
initialized already early on.
Before the patch, function pointers to the PBuffer extensions
were only retrieved in DriverWGL::InitializeExtensionBindings().
However, GpuInit::InitializeInProcess does assume that an
offscreen GL surface can be generated even before this is called.
Task-number: QTBUG-66668
Change-Id: I2dc881a9a04733c0edf000a5d4f582009fd7eb92
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
jpeg_codec.cc contained some implicit conversions to boolean, which
is apparently problematic for some versions of libjpeg. Patch
taken from https://bugs.chromium.org/p/chromium/issues/detail?id=686191
but not backported, since it has not been accepted into chromium yet.
Task-Number: QTBUG-58482
Change-Id: I2c5d5894493d6a7d0698a4e5a7191288a2fdfeb4
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since the introduction of 196ae04aa7c9b274880409fb38a050db99197900
Chromium uses its own ScreenWin implementation on Windows instead
of the previous DesktopScreenQt. This means that a different
implementation of Screen::GetDisplayNearestWindow is called, which
in turn calls ScreenWin::GetHWNDFromNativeView().
This implementation is not complete though, and in Chrome itself it is
overriden inside DesktopScreenWin::GetHWNDFromNativeView() in
chromium/ui/views/widget/desktop_aura/desktop_screen_win.cc, but
WebEngine don't use this file, and it can't be used because WebEngine
doesn't use Aura views.
The proper fix would be to implement logic similar to DesktopScreenWin
inside Qt's own DesktopScreenQt, because currently the implementation
of RenderWidgetHostViewQt::GetNativeView() always returns an empty
pointer.
As a band-aid fix to stop debug builds from crashing (because nothing
really bad seems to happen), is to comment out the assertions.
Task-number: QTBUG-66560
Change-Id: I6d3ece29cd889f5d62e2f21682f1462dde962888
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We still do not use ozone for glx or wayland if
webengine compiled with x11 support. X11 initializer
tries to load egl libraries, this will be
reimplemented with lazy binding in core.
Task-number: QTBUG-65682
Change-Id: I47012f487652e750f223b086e7ca4b224340cc22
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
Add back support for compatibility profile.
Change-Id: I746b53c4622614f847540481cdb43da416ba03b1
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Handles cases where gfx::GetXDisplay() returns null at least for Qt.
Task-number: QTBUG-55384
Change-Id: Ie57c57d7189c279cb5c702325b450f9fb964ac60
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes various issues were we differ from Google's clang.
Task-number: QTBUG-60438
Change-Id: I5a97ba828f7267731e50010c4345caa19bb8939a
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: I62f1048995935995a4f9c84bf636624c6d5ec14c
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows Chromium to fetch the XDisplay owned by Qt instead of a
new one. We were previously overriding MessagePumpForUI::GetDefaultXDisplay
but this was removed along with the switch to Aura.
Change-Id: I9fb53c8cc955f124d88ad0e6ca690f88e816847e
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
Reviewed-by: Jocelyn Turcotte (Woboq GmbH) <jturcotte@woboq.com>
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
If Qt reports the usage of opengl32sw.dll, make sure Chromium also
uses it for rendering.
Change-Id: I61fc0c5a8fa40911d9402a93234b33a735465f38
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
By default the Core Profile is only used on macOS if no --use-gl
command line argument is passed. Depending on this behavior is a bit
risky, thus a new switch option called "opengl_core_profile" is
introduced to allow explicitly using the core profile, for example
when a default QSurfaceFormat is set.
Task-number: QTBUG-60605
Change-Id: Ie927432ab555f0cf4b35c74326c53d0232f98f6a
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: Id51f271047aa03d5480e93835c90a7b0b91bd516
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
There is a Qt implementation of CreateProvider in
src/core/chromium_overrides.cpp
Change-Id: Ibc6bc4e86b7f1f0d8d80e0809d0be7fda3e6e35a
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
We do not need these just because we use most of Aura.
Change-Id: I49f7894bcc6b18b8719ebf59927154730f9e54d2
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add logic to disable the use of the libXss library, while still being
able to suspend power save via the GNOME or freedesktop dbus interfaces.
Change-Id: I97c6f03ba654ba30ad91709028bb0859b8a66de7
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is needed to fetch the MessageLoop, the MailboxManager and the
SyncPointManager of the GPU in-process host.
And fetch the right shared context for the in GPU thread.
Change-Id: I7f38e32b2df11da5b046f16643841d34260c11fb
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| | |
Change-Id: I3c28afbbcc57f43b47ce055db7421abaca1fef63
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: I1d6f3f396d39cccf4275b539919748888b3e19b1
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Exclude source files we override in the qt webengine sources.
Change-Id: I79925220265602bd0c39e5e03162cf1dca15befe
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| | |
Change-Id: Id0fbbdcfa56aa03a71212165ebac16b786cac951
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
ATL currently isn't distributed with MSVS Express, only with the
Professional version. Chromium requires downloading the WDK iso for
express users just to be able to use the ATL version that was shipped
with it.
We can avoid the extra dependency for now by cutting off all the
accessibility code, which is currently the only part of the content
layer depending on ATL. We will use the Qt accessibility code anyway.
Change-Id: Iec25231250ccfc9405fdf342752733814888f348
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We need these if the system EGL is not new enough because the
EGL autobindings are using them.
Task-number: QTBUG-66038
Change-Id: I373152283ff094886ba2d8c263ae840a5feb3555
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
Change-Id: I5471953dbe08ee5afb92d24baeb94863fb8de98e
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When a touchpad is used on macOS, Qt receives both scroll wheel
events and touch events, which it forwards to Chromium.
The gesture detector in Chromium transforms the touch events into
scroll / fling gestures, and these interfere with the original scroll
wheel events from Qt, leading to broken scrolling.
This used to work in Qt 5.7 and lower because the scroll wheel events
had a higher precedence than gestures, but this is not the case
with newer versions of Chromium.
Furthermore the gesture detector in Chromium has the assumption that
it receives touch events from a touchscreen device, and not from a
touchpad, which implies different gesture behaviors (moving one finger
on a touchpad moves the mouse, whereas on a touchscreen it causes the
screen to move, aka scrolling). Thus it is not correct to use the
gesture detector for handling macOS touchpad events.
The fix is a temporary hack which discards scroll and fling gestures
on macOS, thus processing only wheel events received from Qt.
The proper fix will be to remove usage of the gesture detector on
macOS, and rather transform and forward QNativeGestures which
are received directly from the operating system, similarly to how
the Chrome browser handles it.
Task-number: QTBUG-58779
Change-Id: I1b1fc950d033c175aebd617d38591bf5d94b5adc
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Add option to add external ozone platform. Assumes the external ozone
platform is also set as the default ozone platform.
Change-Id: I683b56828f9adbc920fcfc3f63aa3ab8b78a6084
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Fix what appears to be bitrot in the libevent implementation of XEvent
handling so that it works in X11 builds.
Change-Id: Ie348c57a263a2360e623f28c06ebdbf501681749
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since Qt is consuming those textures in a different thread,
synchronizing when commands are handed down to GL isn't always enough.
The GL driver could decide to do additional scheduling and end up
executing Qt's consuming GL commands before Chromium's producing ones
even if they were sent to their respective context in the right order.
gfx::GLFence can now be converted to a POD TransferableFence to allow
waiting for or destroying the sync using a QOpenGLContext, which
gl_fence.cc wouldn't be able to use through Chromium's GL function
table.
Task-number: QTBUG-42295
Change-Id: I5aed0df7adca9c95eda71925399d39fd770fffa1
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
We need to query the EGL extension in qtwebenginecore to avoid directly
accessing EGL methods that may not be linked directly.
Change-Id: Iddd1df70d2dd37964bb0cba70c2a3aa4c67d8002
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
| |
| |
| |
| |
| | |
Change-Id: Ia78a97eea564ed8b8c50ebbdea2eaf7a8dbe6e1f
Task-number: QTBUG-53000
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Removes dependency on libEGL and libGLESv2 on both Windows and X11,
and links to the Qt versions on windows if doing an ANGLE build.
Technically we don't need ANGLE in that case either because we disable
GPU acceleration when Qt is using ANGLE, but since it is runtime
disabled it still need to be there at compile and link time.
Change-Id: I866442d7172609b81eaf83fdba3d8d85cc848cf2
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The PlatformFont support is not implemented in QtWebEngine yet. Thus
without disabling in case of requesting navigation error string (eg.
default message for error page) accessing PlatformFont triggers an
assert.
Change-Id: I9a2b3035e03ecc5c43a50013886ff340f37d8806
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
Reviewed-by: Pierre Rossi <pierre.rossi@theqtcompany.com>
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>
|
|/
|
|
|
|
|
|
|
| |
platforms
Change-Id: I5fecc09e245b75d0fec16756f8d6e6b8f71a143e
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
Reviewed-by: Jocelyn Turcotte (Woboq GmbH) <jturcotte@woboq.com>
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: Idcb1341782e417561a2473eeecc82642dafda5b7
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
|
|
|
|
| |
Change-Id: I0c9831ad39911a086b6377b16f995ad75a51e441
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
|
|
|
|
| |
Change-Id: Ied18ccfc9872b6a5c441218dec17debf93732ea1
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
|
|
|
|
| |
Change-Id: I3c71dd500483eb29491ac3eee4123714dda52da9
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
|
|
|
|
| |
Change-Id: I5485bc5c111539356276457516584fa5737f07d8
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
|
|
|
|
|
|
|
| |
Also imports missing submodules
Change-Id: I36901b7c6a325cda3d2c10cedb2186c25af3b79b
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
| |
Change-Id: I1cae68fe9c94ff7608b26b8382fc19862cdb293a
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
|
|
| |
And add two chrome files we need.
Change-Id: Ie4b6cefa8ea274623132c3ce59f951de8ea4ec6c
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
| |
Change-Id: Iac27464730121b4fac76869d87d622504642e016
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
|
|
|
|
|
| |
Change-Id: Ia93b322a00ba4dd4004f3bcf1254063ba90e1605
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
| |
Change-Id: I2d5eca8117600df6d331f6166ab24d943d9814ac
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
| |
Change-Id: I646c933139007f1fdc42e7a4073652f8e6e55b5a
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|