Did this work before?
  Yes, this used to work prior to ver 49.

Tested the same on win8.1 chrome version 49.0.2623.110 observed that on trying to hover with mouse a small circle is displayed as shown in the screen cast

Could you please let us know if this is the mouse pointer issue you are talking about.

Deleted: Recording #24.mp4 609 KB

Recording #24.mp4 609 KB Download

Attached is screen capture from Chrome version 48 Dev Tools. When you mouse over a DOM element with a CSS :hover class, you actually see the element change, just like you are on a desktop.

The next comment has an attachment from Chrome version 49 Dev Tools. In v49, *all* the modes assume the simulated device is a touchscreen and only offers the "small circle" pointer. This will not trigger any CSS :hover classes.

Device Mode in dev tools should permit general responsive design, which is inclusive of "desktop" devices.

Deleted: dev-tools-hover-chrome-48.mpg 9.3 MB

dev-tools-hover-chrome-48.mpg 9.3 MB Download

Here is the second screen capture, from dev tools v49.

Deleted: dev-tools-hover-chrome-49.mpg 9.2 MB

dev-tools-hover-chrome-49.mpg 9.2 MB Download

Added gif captures to the Gist with all the other related issues:  https://gist.github.com/bseib/be0718842f4c7b31074300f7368e3694#gistcomment-1741768

In the Device Mode overflow menu, you need to select "Show Device Type". Then when in "Responsive" mode, you can select "Desktop" or "Desktop (touch)" as-needed. The default is to always be mobile with touch to encourage mobile-first development.

No bug here, just a place where our UX lacks extremely.

Okay, really dumb question.... Where/What is the "overflow menu"?  I've been poking around looking for a setting that says "Desktop"/"Desktop (touch)", but no luck finding them... :-/

whoops, okay now I feel doubly dumb...

I found the "three dots menu" > User Agent Type > [ Mobile(default) | Desktop | Desktop (with touch) ]

Okay, I see what's going on now, and have the following impression:

When you select anything except the default (mobile), then there is visual feedback telling you the mode you are in. This visual feedback guides you where to look for changing that mode. For example, "desktop" is shown in the upper right:

 [device-mode-desktop.png]

And even if you change the pixel density, this info is reflected in the same area, near the overflow menu.:

 [device-mode-desktop-dpr2.png]

And selecting "touch", shows similar mode feedback:

 [device-mode-touch.png]

But mobile, being default, does not provide any indication that's I'm in any particular mode, or where/how I might change it:

 [device-mode-mobile.png]


I totally agree with encouraging mobile first. In that regard I think it is smart to make the defaults reflect a mobile device. But all the other modes (pixel density, network speed, agent type) should have equitable presence in the UI. That is, I should initially see a screen aimed at developing for mobile, but I can very easily toggle it into desktop/tablet/touch/offline modes, etc.

At this point, I doubt I'm saying anything you don't already know. I don't mean to be annoying -- just trying to be thorough in capturing my experiences while they are fresh and new to me. I look forward to the next iteration of these tools.



https://gist.github.com/bseib/be0718842f4c7b31074300f7368e3694#gistcomment-1741862

Deleted: device-mode-desktop.png 85.8 KB

	device-mode-desktop.png 85.8 KB View Download

Deleted: device-mode-desktop-dpr2.png 90.1 KB

	device-mode-desktop-dpr2.png 90.1 KB View Download

Deleted: device-mode-touch.png 85.4 KB

	device-mode-touch.png 85.4 KB View Download

Deleted: device-mode-mobile.png 93.8 KB

	device-mode-mobile.png 93.8 KB View Download

Thank you for providing more feedback. Adding requester "tkonchada@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://sites.google.com/a/chromium.org/dev/issue-tracking/autotriage - Your friendly Sheriffbot

 broc.seib@ Thanks for the update.

could you please provide us any sample test file or URL to triage the issue from test team end.

Thanks,

Hey Dmitry, 

I think you would be interested in this feedback.

We have changed this a bit in last version trying to unify the options. Could you please take a look at canary and tell us what you think? 

@kavvaru the url for the page I was testing with is:

  http://ianlunn.github.io/Hover/

However, this report may be moot since I *can* see the correct hover behavior by selecting "desktop" mode. It just wasn't obvious how to do that. So this is really more of a UX issue for this screen in general, and perhaps should be closed, or referenced in other related issue.

@dgozman I just checked out the Canary channel, Version 51.0.2701.0 canary (64-bit)

Fantastic! Being able to see pixel density, device type, and network bandwidth prominently displayed and changeable is what we needed. And being able to change their visibility via toggles in the overflow menu are also very appropriate. What is one person's clutter is another's treasure.

Now that overflow menu needs a choice to toggle being centered, or left-aligned.

The only other inequity is the lack of resizer bars when you select a mobile device. Yes, preset mobile devices are not resizable in real life. But I shouldn't have to poke around to find a setting to let me simply resize the width from the condition that happens to present itself *now*. If I select the Responsive option, then it resizes everything unexpectedly. I already have some comments on that topic in  issue 598822 , and probably need to add some more info there.

Deleted: show-options-in-overflow.png 53.7 KB

	show-options-in-overflow.png 53.7 KB View Download

Alright, let's keep the resizer discussion in  issue 598822  then. I'll close this one as the new version addressed the concerns.