diff options
| author | Allan Sandfeld Jensen <allan.jensen@qt.io> | 2018-08-31 14:37:56 +0200 |
|---|---|---|
| committer | Allan Sandfeld Jensen <allan.jensen@qt.io> | 2018-09-22 08:47:28 +0000 |
| commit | 75fcb640fae72446b26d7978a5df3c058e0ab67f (patch) | |
| tree | 3467a5d3eb1f31337b81ab8976a07cac0e694541 /src/core/web_engine_context.cpp | |
| parent | 06e3d201299ab803f4dc41f35201830c74242d19 (diff) | |
Adapt to forced scroll-wheel latching
Handle that Chromium now requires all wheel events to be phases despite
them not being phased on the majority of platforms.
Change-Id: Iabd5630652c0d8fd67563db3d63ef1f2f528c35c
Reviewed-by: Michael Brüning <michael.bruning@qt.io>
Diffstat (limited to 'src/core/web_engine_context.cpp')
| -rw-r--r-- | src/core/web_engine_context.cpp | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/src/core/web_engine_context.cpp b/src/core/web_engine_context.cpp index 4b0a2f6cd..e2c127b22 100644 --- a/src/core/web_engine_context.cpp +++ b/src/core/web_engine_context.cpp @@ -417,8 +417,6 @@ WebEngineContext::WebEngineContext() appendToFeatureSwitch(parsedCommandLine, switches::kEnableFeatures, features::kAllowContentInitiatedDataUrlNavigations.name); // Surface synchronization breaks our current graphics integration (since 65) appendToFeatureSwitch(parsedCommandLine, switches::kDisableFeatures, features::kEnableSurfaceSynchronization.name); - // Scroll latching expects phases on all wheel events when it really only makes sense for simulated ones. - appendToFeatureSwitch(parsedCommandLine, switches::kDisableFeatures, features::kTouchpadAndWheelScrollLatching.name); if (useEmbeddedSwitches) { appendToFeatureSwitch(parsedCommandLine, switches::kEnableFeatures, features::kOverlayScrollbar.name); |