Commits (14)
-
Friedemann Kleint authored
Change-Id: Id54fd7ca704bd9456c98765afdbaf04e3d46b33c Reviewed-by:
Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>
3d40d9eb -
Friedemann Kleint authored
Change-Id: I528b7c4c22a1c47f54fe1b78a9d781a6af9cfc6b Reviewed-by:
Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>
35216895 -
Peter Varga authored
Change-Id: Id2e62af31f1dc5268fe6b163d2fc0b671f5e491a Reviewed-by:
Andras Becsi <andras.becsi@digia.com>
9e10b7a8 -
Friedemann Kleint authored
The default size causes qt.io to look bad and is too small for high resolution screens. Change-Id: Ie417dde8ab32fc4897cd60c292afdc39b9213510 Reviewed-by:
Andras Becsi <andras.becsi@digia.com>
32f75b83 -
Allan Sandfeld Jensen authored
The feature enum names and documentation gave the impression it could control audio and video output, while they only control input. Also removed documentation of non connected feature permissions for Notifications and GeoLocation. Change-Id: Ia35142ca691ebd6059b7472e9803fda8cbd84813 Reviewed-by:
Jocelyn Turcotte <jocelyn.turcotte@digia.com> Reviewed-by:
Pierre Rossi <pierre.rossi@gmail.com>
d2d5baeb -
Allan Sandfeld Jensen authored
We should save our cache in the configured CacheLocation, and ensure we are prepared for multiple BrowserContext by caching to a Default subdir. This matches how chromium caches on linux. Change-Id: Ibe914fca35435ea1658565be87747cfabc71e97b Reviewed-by:
Jocelyn Turcotte <jocelyn.turcotte@digia.com>
f343e9d6 -
Oswald Buddenhagen authored
Change-Id: I01615a492c958bf123deeef5d2ddf9fb01b1a9d0
e929af14 -
Szabolcs David authored
Change-Id: I7cb497ce0f67eaf948caa88930fa1a3040ff4c39 Reviewed-by:
Andras Becsi <andras.becsi@digia.com>
aa1b2d20 -
Andras Becsi authored
Change-Id: I2d04e910c7a08e1c630bc490d1f8b1be3d27a6f1 Reviewed-by:
Jocelyn Turcotte <jocelyn.turcotte@digia.com>
81d94e61 -
Jani Heikkinen authoreda4c77433
-
Jocelyn Turcotte authored
ANGLE isn't thread-safe and we're already taking a risk by letting Chromium do texture upload from the GPU thread with a shared GL context. Any kind of drawing happening concurrently between the GPU thread and the Qt scene graph thread might currently end up drawing on the same device context and this is creating visual artifacts and Direct3D errors. We're already disabling WebGL but we should also disable accelerated 2D canvas rendering to lower that risk. We should ultimately disable ANGLE from within Chromium or fix multithreading issues to properly support GL rendering scenarios across threads. Task-number: QTBUG-41627 Change-Id: I37a7a778f0e1066a454f51bb38e98df4dea8767e Reviewed-by:
Pierre Rossi <pierre.rossi@gmail.com> Reviewed-by:
Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>
4f4a3346 -
Oswald Buddenhagen authored
Change-Id: I3b7df1ada08a8985734d804208b50cd5e0403903
06ad5d54 -
Robin Burchell authored
Callers inside Chromium expect an implementation of AccessTokenStore to exist. This fixes crashes with the geolocation-based APIs, exposed on e.g. google.com when faking an Android UA (as well as other places, probably). Change-Id: I45e6b483e096d5165fefd86927cdf34e799cc4d9 Reviewed-by:
Pierre Rossi <pierre.rossi@gmail.com>
85d26a29 -
Zeno Albisser authored
We are mapping a single QTouchEvent to multiple MotionEventQt for Chromium. For gesture recognition it is important that these motion events are being processed in a sorted manner, as a move event might trigger a different gesture depending on how many ACTION_DOWN or ACTION_POINTER_DOWN were received before. It is particularly illegal to process an ACTION_MOVE with multiple touch points without having received a ACTION_POINTER_DOWN before. Change-Id: I75d22dd845774a14b5f590e0e0ce46263c4a49f4 Reviewed-by:
Jocelyn Turcotte <jocelyn.turcotte@digia.com> Reviewed-by:
Andras Becsi <andras.becsi@digia.com>
51d7318a
Showing