New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 689611 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Add option to disable touch emulation in developer tools

Project Member Reported by jfweitz@chromium.org, Feb 7 2017

Issue description

Chrome Version: 56.0.2924.76 (Official Build) beta (64-bit)
OS: Mac OS X 10.12.3

What steps will reproduce the problem?
(1) Open dev inspector
(2) Emulate a mobile device (like iPhone)
(3) Try to disable touch emulation

If you go to "sensors" the options listed are "Device-based" and "Force enabled".
Please add a "Force disabled" option.

 
Owner: dgozman@chromium.org
Status: Assigned (was: Untriaged)
Status: WontFix (was: Assigned)
Switch to responsive and pick non-mobile device type for that.
In our use case we often need to emulate a mobile a mobile device regarding size, user agent, network conditions and sometimes is useful to disable touch emulation:
- Sadly sometimes you have tooling for debugging js/html/css that doesn't handle touch well.
- You want more precision 
- You can actually use a mouse with an android mobile phone/tablet which uses a cursor pointer AFAIK.


Choosing a mobile device and then changing to responsive changes the UA which makes debugging harder as navigations will use a different UA if you don't remember to switch back to mobile device.

Sign in to add a comment