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

Issue 613504 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

deviceorientationabsolute event cannot be listened on Chrome for Windows

Project Member Reported by wanming....@intel.com, May 20 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.102 Safari/537.36

Steps to reproduce the problem:
1. run https://timvolodine.github.io/deviceorientation-test/ on Chrome 50 stable for Windows Surface

What is the expected behavior?
Values in 'deviceorientationabsolute' should be presented

What went wrong?
window.addEventListener('deviceorientationabsolute', onOrientationAbsolute) cannot be listened

Did this work before? N/A 

Chrome version: 50.0.2661.102  Channel: stable
OS Version: 8.1
Flash Version: Shockwave Flash 21.0 r0
 
Cc: rnimmagadda@chromium.org
Labels: Needs-Feedback
@wanming.lin: Could you please have a look at the attached video and let us know if this is the correct procedure to repro this issue.

Else, provide us the screen-recording for better understanding.

Thank you.
613504.mp4
805 KB Download
Yes, but you must run this test on the device which has the capability of DeviceOrientation.
Project Member

Comment 3 by sheriffbot@chromium.org, May 23 2016

Labels: -Needs-Feedback Needs-Review
Owner: rnimmagadda@chromium.org
Thank you for providing more feedback. Adding requester "rnimmagadda@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: IO>DeviceOrientation
Labels: -Needs-Review M-51
Owner: ----
Status: Untriaged (was: Unconfirmed)
Able to repro this issue on Windows 8.1 [Lenovo Think Pad - Surface] for Google Chrome Stable Version - 51.0.2704.79 

This is a Non-Regression issue existing from M30 - # 30.0.1549.0
Screenshot (1).png
171 KB View Download
Screenshot (2).png
142 KB View Download

Comment 5 by mcasas@chromium.org, Feb 27 2017

Cc: mcasas@chromium.org ningxin...@intel.com wanming....@intel.com
 ningxin.hu@, wanming.lin@, how does this bug relate to
 https://crbug.com/224849  ? I.e. are they both the same and they 
just point to a missing implementation backed?  (If so I'll merge
this one into that one and rename it to make this clearer).

Comment 6 by mcasas@chromium.org, Feb 27 2017

Labels: -M-51 Needs-Feedback
Owner: timvolod...@chromium.org
Status: Assigned (was: Untriaged)
absolute device orientation was implemented on windows here:
https://codereview.chromium.org/1986263003/

which I believe should be M52. Looks like the Chrome version used on this bug is 50/51. So trying with Chrome 52+ should resolve the issue.

Status: WontFix (was: Assigned)
please reopen if persists with Chrome 52+
Components: -IO>DeviceOrientation Blink>Sensor

Sign in to add a comment