| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes Chromium Content API to be able to notify about text
selection changes triggered by non-user events (eg. JavaScript, IME,
autofill).
Based on:
https://codereview.chromium.org/2903833002
Corresponding Chromium bug report:
https://bugs.chromium.org/p/chromium/issues/detail?id=671986
Change-Id: I86a7f203d789853199469b301facd06fe5ba54bd
Task-number: QTBUG-53134
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
http://crrev.com/2384163002 skipped initializing RenderSandboxHostLinux
If the sandbox and zygote are both disabled. But the RendererSocket is
used even in this case by the Linux ChildProcessLauncherHelper, so it
lead to a crash.
Instead initialize the RenderSandboxHostLinux unconditionally. This
appears to be what some code expects in multi-process code.
Tested:
cr run chrome --no-zygote --no-sandbox http://www.google.com
BUG=712779
Change-Id: I391205092c13c6c2a4e7c59c74729d2b068dcb9f
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The problem was that sometimes a find reply would come in from a frame that
has already been removed. This was assumed not to be possible (which is the
reason for the original DCHECK present). The right thing to do is just
ignore these replies, so the DCHECK has been turned into an early exit.
BUG=624738
Review-Url: https://codereview.chromium.org/2399923002
Cr-Commit-Position: refs/heads/master@{#458551}
Change-Id: I94f27a4f17a5a27b56a78c09e1b9b5e8f059f2a2
Task-number: QTBUG-60472
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
|
|
|
|
|
|
|
| |
The windows fonts warmup was using a PPAPI locks.
Task-number: QTBUG-61170
Change-Id: If8370667091ead3c5b96f2661796892395fdd76b
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
|
|
|
|
|
|
|
|
|
| |
Return MEDIA_DEVICE_NOT_SUPPORTED to JavaScript instead of triggering DCHECK in
MediaStreamManager::SetupDeviceCaptureRequest.
Task-number: QTBUG-60832
Change-Id: Iadb99244fc4345580faa1a3a1af3264d91c3fa8f
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Service Workers may be loaded over different schemes than HTTP(S)
(chromium itself provides interfaces to register schemes for this!).
Despite this, chromium assumes in many places, that Service Workers
were always loaded over HTTP(S). The code for registering Service
Workers often blindly dereferences the requests "header" pointer
without checking it for NULL beforehand and assumes the status code
to be an HTTP status (implying an error if it is not between
200 and 299).
Task-number: QTBUG-56169
Change-Id: Id63789bbe974e1958981b651ccc15cfbb067b4af
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When v8_use_external_startup_data is disabled natives_blob.bin and
snapshot_blob.bin external files are not generated. Skip try to open
them for their file descriptors to suppress "Ignore invalid file" error
messages due to non-existent files.
This change adds back guards removed in
https://codereview.chromium.org/2684433003
Change-Id: I0bb93c0e05df18905083423a84d1e56c22232e4d
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Service Workers may be loaded over different schemes than HTTP(S)
(chromium itself provides interfaces to register schemes for this!).
Despite this, chromium assumes here, that Service Workers
were always loaded over HTTP(S). The code for registering Service
Workers blindly dereferences the requests "header" pointer
without checking it for NULL beforehand.
Task-number: QTBUG-56169
Change-Id: If7ba87fbf0cc032cc3b3c34d9d4e0d1041c93178
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
|
|
|
|
|
|
|
| |
Fix a few issues triggered while trying to build on mac after the
rebase on Chromium 58
Change-Id: I998d104862d807caa6b176c62bebc9e57461968b
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
|
|
| |
This file doesn't exist in sources, and the change was lost in rebasing
Change-Id: I33d604ecdac86db97bf7f29f9d759f34bf6ef17c
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
|
|
|
|
|
|
| |
Part lost in rebase.
Change-Id: Id6851ea0678ec8e85ea75913977776e4d014c36c
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
|
|\
| |
| |
| | |
Change-Id: I8c280ca9068fdda9cf6276725bfb8608eccb497a
|
| |
| |
| |
| |
| | |
Change-Id: Ib913750d687f29e036959c62a0cabf2412a8faa7
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The deployment target will always be higher than 10.9, because
Qt 5.9 requires it to be at least 10.10.
Task-number: QTBUG-60438
Change-Id: I5a97ba828f7267731e50010c4345caa19bb8939a
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Due to change 8ae5d7f0 in chromium DWriteFontProxy is now
also initialized when not using the sandbox. This triggers
on win10 DCHECK which fails if font fallback is supported,
but reported windows version (due to missing correct
manifest file) is 8.0. Skip the DCHECK for qtwebengine
builds.
Change-Id: I6fcef46b1e0f0dc8fec8fec62cc46322efcaaad9
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With the remote inspector, the internal server creates the clients, and
we in the external API does not know the client. The devtools agent host
impl does however and can stop being stupid and force us to guess.
Change-Id: I55a79cc90d39e6203d74a63ce86575599fe58232
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
WebSpeech requires Google API keys, so we do not support it, and
disabling it also gets rid of libspeex and libFLAC.
Change-Id: I80a54ec4c6a13ea4c443289aa42369196c2e095a
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
| |
| |
| |
| | |
Change-Id: I1d6f3f396d39cccf4275b539919748888b3e19b1
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
This allows removing the catapult dependency
Change-Id: Ia2bf777b07e9f88e28d6637bf3aab5d6a97ca7e6
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows us to give our own feedback on the console about the
outcome of the server socket binding, outside of the Chromium
logging.
Change-Id: Ib16dd97b6f5e07ad2e889d3c4520b2fda1eb532b
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
| |
| |
| |
| |
| |
| | |
Exclude source files we override in the qt webengine sources.
Change-Id: I79925220265602bd0c39e5e03162cf1dca15befe
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
USE_AURA is not set for the macOS build of Qt WebEngine. Thus enable the
corresponding code with QT_TOOLKIT macro instead.
Change-Id: Ie6b053984fa582bc54d05c5d13d83f5d1d706c25
Task-number: QTBUG-55766
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A method was not defined but still used when building with plugins
disabled. Checking original chromium history, the ifdef block seems
like an oversight and is safe to remove. The method contents does not
depend on any plugin code.
Change-Id: I1aff3abc352faf545fb82d5ea0139a911c0722be
Reviewed-by: Michael Brüning <michael.bruning@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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Changes the assert to a logged error.
Task-number: QTBUG-50566
Change-Id: I70f315553bfde53db3b4c4b57cf46f2f42c4260d
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
Reviewed-by: Viktor Engelmann <viktor.engelmann@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add notifications if dictionary can not be loaded,
do not delete corrupted files, simplify naming
of dictionaries - do not use hardcoded region
language mapping.
Change-Id: Ifcc7952e5815cadf7aeb64577988749c0d1a604d
Reviewed-by: Kai Koehne <kai.koehne@qt.io>
|
| |
| |
| |
| |
| |
| | |
Change-Id: Idaeffa4045f631171e6a99d63a7aef7caa80e782
Task-number: QTBUG-56261
Reviewed-by: Michal Klocek <michal.klocek@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The Windows platform plugin already calls OleInitialize. When
ScopedOleInitializer detects that OleInitialize was already called it
will yield an error message. This is not much of a problem but unsettles
users.
Task-number: QTBUG-53746
Change-Id: If5e978c6ef022a7ec0637a2e171fc0f9b3e92a41
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
We currently do not support the SUID sandbox and the error
pollutes the auto tests output.
Change-Id: I2675aa2e03394f1c03e4df6bd1b21764ed19206a
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Chromium expected fullscreen mode to be accepted or rejected
synchronously, that fits poorly with our API, so instead we add the
option to signal when fullscreen mode actually changes.
Change-Id: I72b93417790cf273194df480a220a498a71deb74
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
To enable standard webview API including javascript injection we need
to be allowed to enabled it like the Android webview does.
Change-Id: I3e8bcaa4508a65f7d8f56671e86c6ac4f44d0ca4
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
The UI layer needs to have the selection updated also when the selection
is not valid because it has been cleared.
Change-Id: I86dac087a8ea94fca4a91a2667658395b65e6046
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
By disabling this preference blink will be able to tell if fullscreen
is supported before requesting it and will not show non-functional
fullscreen buttons on youtube and other HTML5 videos.
Change-Id: I2ed3828931e99295b634e6945d8ab97a1e8a34dd
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These threads are using the UI message loop on Windows per default. This
won't work since the UI message loop is handled by Qt and the Renderer
and GPU threads won't work with it properly.
Force these threads for using the default message loop as they use it on
Linux platform.
Change-Id: I8b04ba9070912378cf1d13173ddff48e98f9a49b
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| | |
This patch makes webfonts to read the fontconfig defaults for
their size and font style.
Change-Id: I80ffd8e2ff27d438c60457ca2b1836999e528783
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
NSAutoreleasePool init and dray must be symetrical and we can't guarantee
that for ContentMainRunner as well as Chromium can since we initialize
the ContentMainRunner on-demand but destroy it with the QCoreApplication's
destruction.
We also don't need to use it since any allocation that
ContentMainRunnerImpl::autorelease_pool_ would cover is already covered
at the bottom of the stack by the QCocoaAutoReleasePool in
QCocoaEventDispatcher::processEvents.
Change-Id: I2874916420457e3d36d08fb9fca0d919f374f592
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We use RenderWidgetHostViewQt, not RWHVMac, even on macOS.
Since some platform decisions seem to have transpired all the way to
the content layer, we should simply use the web ui for select elements
on mac for the time being.
Change-Id: Ib430f8686862cf0958ccdbfefb8bfa36af590e97
Reviewed-by: Alexandru Croitor <alexandru.croitor@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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| | |
We do not support loading the chrome://tracing WebUI and therefore
we shouldn't bundle those resources in our library.
Change-Id: If3aa4c676b22a55e772f19487e21b4cd48babe65
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conditionally running SetupSignalHandlers in the content main runner
led to crashes when SIGPIPE was not ignored.
Task-number: QTBUG-44689
Change-Id: I0eddf52b9f760a23cc66ea5079b87f80d688cbdb
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
By default chromium installs a new_handler that calls exit() when
new/malloc fail to allocate memory. While this is a reasonable thing
to do for a browser, a library should leave the decision to the user.
Change-Id: Ice5ff8a3347a9df836fb298fed1e80bf21e6b7dc
Task-number: QTBUG-45459
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds a boolean to ContentMainParams that we can set to false in
the WebEngineContext in order to not overwrite the signal handlers
that may be set by the application using QtWebEngine.
Task-number: QTBUG-42747
Change-Id: If9b7a66019594245545edf891fec4e5cf62dcf4a
Reviewed-by: Jocelyn Turcotte <jocelyn.turcotte@digia.com>
Reviewed-by: Jocelyn Turcotte (Woboq GmbH) <jturcotte@woboq.com>
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
BrowserAccessibilityManagerQt derives from
BrowserAccessibilityManager. Exactly as on
Windows or Mac, we therefore need our own
implementation of the Create function.
Change-Id: I3ead20628c3da32bb60c45afc2eff44c8cf081b2
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>
|
| |
| |
| |
| |
| |
| | |
Change-Id: I1ffb47a299e5b17e3c2c463f592603170fc444f4
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>
|
|/
|
|
|
|
|
|
|
| |
Instead we export _override symbols and add the symbol
renaming directly into the QtWebEngineProcess source.
Change-Id: I15049609dd77be6de2a2398f25a37fff1b6f5519
Reviewed-by: Andras Becsi <andras.becsi@theqtcompany.com>
Reviewed-by: Michael Brüning <michael.bruning@theqtcompany.com>
|
|
|
|
|
| |
Change-Id: I67f57065a7afdc8e4614adb5c0230281428df4d1
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
|
|
|
|
|
| |
Change-Id: I29db402ff696c71a04c4dbaec822c2e53efe0267
Reviewed-by: Peter Varga <pvarga@inf.u-szeged.hu>
|
|
|
|
|
| |
Change-Id: I4e04de8f47e47e501c46ed934c76a431c6337ced
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
|