diff options
| author | Florian Bruhin <me@the-compiler.org> | 2019-05-22 18:29:16 +0200 |
|---|---|---|
| committer | Florian Bruhin <me@the-compiler.org> | 2019-05-23 14:12:03 +0200 |
| commit | 819aa370ec413ba1ea4506d591d4debe87c21831 (patch) | |
| tree | d16c9b5c4b3d3764f86957b78bac18f6fee13973 /examples | |
| parent | 02c01aedcc08525eea226382318f6a8585c3dae7 (diff) | |
Claim to support hover
Chromium sets those settings based on ui::GetAvailableHoverTypes() and
GetPrimaryHoverType() which (on Linux) use an InputDeviceManager to check
whether there's a mouse or touchpad present.
With them being unset, CSS media queries (hover/any-hover) tell websites that
hovering isn't supported:
https://developer.mozilla.org/en-US/docs/Web/CSS/@media/hover
https://developer.mozilla.org/en-US/docs/Web/CSS/@media/any-hover
On some websites such as GitHub, this disables/breaks hovering functionality.
QtWebEngine can't figure out whether it's running on a device with a
mouse/touchpad (using Chromium's code won't work as no InputDeviceManager is
available, and Qt doesn't seem to have any comparable functionality). However,
since QtWebEngine is not available for mobile platforms, assuming that a mouse
is present (rather than assuming that none is) seems reasonable.
Change-Id: Ie038318f105bafdf955d512ab10f13f33da1111b
Fixes: QTBUG-75894
Reviewed-by: Jüri Valdmann <juri.valdmann@qt.io>
Diffstat (limited to 'examples')
0 files changed, 0 insertions, 0 deletions