[Generic Sensor]the sensor frequency is incorrect on Linux platform
Reported by
canx....@intel.com,
Dec 21 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: Test Cases: https://honry.github.io/demo/tests/sensors/Accelerometer.https.html https://honry.github.io/demo/tests/sensors/Gyroscope.https.html https://honry.github.io/demo/tests/sensors/Magnetometer.https.html 1.Run test case 2.Check the test result which test that the frequency hint is correct. What is the expected behavior? The frequency hint is correct What went wrong? The frequency hint is incorrect Error Message: assert_equals:expected 3 but got 2. BTW,I run layout test by command line: ./blink/tools/run_layout_tests.py third_party/WebKit/LayoutTests/sensor all of the sensor test cases got pass result. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 57.0.2950.4 Channel: dev OS Version: Ubuntu 16.01 Flash Version: Shockwave Flash 24.0 r0
,
Dec 21 2016
,
Dec 21 2016
,
Dec 26 2016
,
Dec 27 2016
canx.cao@, recently we bound sensor reading update/notification to actual frame rate (https://codereview.chromium.org/2604483004), so some fluctuations in 'onchange' calls frequency are possible. I think the tests you are referencing should be updated same way as the layout-tests are updated: https://codereview.chromium.org/2604483004/diff/20001/third_party/WebKit/LayoutTests/sensor/resources/generic-sensor-tests.js |
||||
►
Sign in to add a comment |
||||
Comment 1 by mikhail....@intel.com
, Dec 21 2016