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

Issue 756376 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Device orientation doesn't change in 'Sensors' section of devtools.

Reported by rp...@etouch.net, Aug 17 2017

Issue description

Version: 62.0.3188.0 a6c5719b8b51fe9ac7af8af1ce8318a83b70b486-refs/heads/master@{#495023}
OS: Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.11.6,10.12.3)

What steps will reproduce the problem?
1. Launch chrome, navigate to NTP and open devtools.
2. Now press 'Esc' key to open 'Console Drawer' and click on 'More actions' iron icon and open 'Sensors'
3. Now click on 'Orientation' select 'Custom orientation' and click and hold on up arrow of 'Gamma' and release it and again do the same,observe
 
Actual: Device orientation doesn't change after clicking and holding of mouse pointer on up/down arrow of Alpha/Beta/Gamma.
Expected: Device orientation should change after clicking and holding of mouse pointer on up/down arrow of Alpha/Beta/Gamma.

Note: Device orientation changes for the first instance as mentioned in step 3.

This is regression issue, broken in ‘M 58’ and will soon update other info :
Good build:58.0.2994.0
Bad build: 58.0.2995.0
 
Actual_video.mp4
2.0 MB View Download
Expected_video.mp4
1.3 MB View Download
Labels: Needs-Bisect
Status: Untriaged (was: Unconfirmed)

Comment 2 by l...@chromium.org, Aug 17 2017

Owner: l...@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by rp...@etouch.net, Aug 18 2017

Labels: -Needs-Bisect hasbisect
Below is the bisect info for this issue :

Narrow bisect info:
https://chromium.googlesource.com/chromium/src/+log/07c6e27a5cea714d7fdfbb297b998a531eb45371..8580766009627c5aeb0625172c3f3c576d7c3636?pretty=fuller&n=100

Comment 4 by l...@chromium.org, Nov 17 2017

Status: WontFix (was: Assigned)
Thanks for the report.  This might look strange, but is working as intended.  The browser doesn't register the successive clicks as having changed the input until the mouse is moved.

This happened after 
https://chromium.googlesource.com/chromium/src/+/65954e8e284b23dcaccc6fa07246d31df3a1255a

and can be reproduced similarly with this small example
https://jsfiddle.net/e7zpu47m/1/

Sign in to add a comment