Issue metadata
Sign in to add a comment
|
Media query on a desktop Ubuntu 17.10 installation incorrectly indicates no hover support
Reported by
n...@forefrontanalytics.com.au,
Dec 26 2017
|
||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36
Steps to reproduce the problem:
1. Open Chrome dev tools console on Ubuntu 17.10 running a desktop machine
2. Enter in console: $ window.matchMedia('(hover: none)').matches
What is the expected behavior?
Should return 'false' as Chrome on a desktop supports hover
What went wrong?
Returned 'true'
Did this work before? N/A
Does this work in other browsers? Yes
Chrome version: 63.0.3239.108 Channel: stable
OS Version: Ubuntu 17.10
Flash Version:
Reproduced on 3 different Ubuntu 17.10 machines
Works correctly on Firefox Ubuntu 17.10
Works correctly on Chrome Ubuntu 17.04
,
Dec 28 2017
,
Dec 28 2017
Able to reproduce the issue on reported version 63.0.3239.108 and this works fine on 52.0.2707.0 using Ubuntu 17.10. Issue is not seen on Ubuntu 14.04, working on bisect and will update the results
,
Dec 28 2017
,
Dec 29 2017
Able to reproduce the issue on reported version 63.0.3239.108 and latest canary 65.0.3305.0 Ubuntu 17.10 hence providing Bisect Info This issue is specific to Ubuntu 17.10 Bisect Info: ================ Good build: 60.0.3102.0 Bad build: 60.0.3103.0 You are probably looking for a change made after 472529 (known good), but no later than 472537 (first known bad). https://chromium.googlesource.com/chromium/src/+log/f989595632258d0cd667e7ef74ad5aec874329bc..b1cf560ccc8850e6fd059c3f32cde1a88787537b Review-Url: https://codereview.chromium.org/2827803002 Suspecting the same changelog @kolos: Please confirm the issue and help in re-assigning if it is not related to your change. Thanks!
,
Dec 29 2017
,
Aug 9
I can't repro on gLinux 70.0.3514.0. ned@forefrontanalytics.com.au: does this still repro for you?
,
Aug 21
I believe I also have run into this bug on Chrome Version 68.0.3440.106 (Official Build) (64-bit), under Ubuntu 17.10 with the default GNOME desktop environment. I've tried umpteen examples of how to use @media (hover: hover) in CSS and none of them are working as described. Notably, it doesn't work for me in Firefox either, even using their own official example at https://developer.mozilla.org/en-US/docs/Web/CSS/@media/hover . That suggests to me that the problem may be with Ubuntu or GNOME - that both browsers are retrieving information on device capabilities from the underlying desktop environment, and that information is incorrect.
,
Aug 23
The NextAction date has arrived: 2018-08-23
,
Aug 23
Re#8: Thank you for the additional information, that's helpful. Could you try Chrome Dev channel? Ping: ned@ can you please confirm if the issue still repros for you? You can use https://bokand.github.io/mq.html - matching media queries are highlighted in green. alexis.menard@: Ping - could you take a look at the issue? Your patch is in the bisect range.
,
Aug 27
I'll take a look this week.
,
Aug 30
The NextAction date has arrived: 2018-08-30
,
Aug 31
I can't reproduce that problem. Here are two screenshots on two different Ubuntu Desktop machines. Both have keyboards and mouse connected. Ubuntu Version : 16.04 Kubuntu Version : 18.04 Both machines are behaving correctly. I need more infos on your machine. If Firefox is not behaving as expected as well, I'm guessing that most likely there is something funky in your OS. We use evdev from the kernel to get the input methods, I suggest you start looking there if it's listed as it should.
,
Sep 25
I'm no longer seeing this issue in Chrome 69.0.3497.100 on Ubuntu 18.04. I'm afraid I don't have access to a machine with Ubuntu 17.10 to test on that.
,
Dec 3
Closing, feel free to comment if this issue can be reproduced. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Dec 26 2017