Desktop (touch) is also odd or feels incomplete. It shows a coarse pointer with touch events enabled, but only has any-pointer:fine and any-hover:hover exposed. No sign of primary pointer or coarse pointer reflecting the given cursor and non-hover environment.

Tested on Mac OS X 10.11.6 with Chrome Stable 53.0.2785.143 and observed the following:

1. Opened sample page Google in responsive mode.
2. Executed "window.matchMedia("(pointer: any-hover").matches" and "window.matchMedia("(hover: hover").matches" on console .
3. Got result as "False" 

Attached screen cast for the reference. Could you please confirm , whether this is the correct procedure followed and if it is the same issue that you have faced.

Thank You !

Right, that's correct. I just forgot to mention the 'false' results in clear terms.

Please note however, that there are 4 responsive modes:
"Mobile (no touch)" Responsive Mode is for my first comment.
The second observation is for the "Desktop (touch)" context.

Pointer Media queries were manually customized for each of all four modes. But fairly incorrectly for those two specific modes to match the expected simulated environment.

Tested the following scenario:

Changed the responsive mode to "laptop with touch" and executed the following commands:

window.matchMedia("(pointer: any-hover").matches  result is "false"

window.matchMedia("(hover: hover").matches result is "true"

Could you please confirm is this the same as the issue you faced. If you can provide us screen cast , that would be helpful for us to triage the issue in a better way.

Thank You !

No. There is no 'laptop with touch' by default in Chrome 53 that I can see. I don't know know where you get this. Let me reiterate the repro step by step in details.

On a non-touchscreen desktop computer:
1. Open http://www.hexanet.com/test/nav.htm in responsive mode.
2. Enable "add device type". See snapshots.
3. Then select "Mobile (no touch)" Responsive Mode
4. Reload the page.
5. Execute "window.matchMedia("(pointer: any-hover").matches" and "window.matchMedia("(hover: hover").matches" in console .
6. Both are "false".

Now if you move your mouse over BUTTON+LINK, it will trigger a hover. Therefore at least window.matchMedia("(pointer: any-hover").matches should be true.

Deleted: Enable-Responsive-Device-Types.png 198 KB

	Enable-Responsive-Device-Types.png 198 KB View Download

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/40188e38e26f3e3dab90524c9698dbfa1113c2f4

commit 40188e38e26f3e3dab90524c9698dbfa1113c2f4
Author: Dmitry Gozman <dgozman@chromium.org>
Date: Thu Aug 17 02:00:25 2017

[DevTools] Make touch emulation, not mobile device emulation, affect hover/pointer MQs

Bug:  530183 ,  653285 
Change-Id: I60457c5f784decf3a21c040b20a636c99017c411
Reviewed-on: https://chromium-review.googlesource.com/617417
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Commit-Queue: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#495049}
[add] https://crrev.com/40188e38e26f3e3dab90524c9698dbfa1113c2f4/third_party/WebKit/LayoutTests/inspector-protocol/emulation/touch-emulation-expected.txt
[add] https://crrev.com/40188e38e26f3e3dab90524c9698dbfa1113c2f4/third_party/WebKit/LayoutTests/inspector-protocol/emulation/touch-emulation.js
[modify] https://crrev.com/40188e38e26f3e3dab90524c9698dbfa1113c2f4/third_party/WebKit/Source/core/exported/WebFrameTest.cpp
[modify] https://crrev.com/40188e38e26f3e3dab90524c9698dbfa1113c2f4/third_party/WebKit/Source/core/inspector/DevToolsEmulator.cpp