Ringmark test fail
Reported by
ruch...@samsung.com,
Mar 15 2018
|
|||||||||||
Issue descriptionSteps to reproduce the problem: 1. Open url rng.io in chrome browser 2. Observe What is the expected behavior? Ringmark is a web-based test suite that measures how well a mobile browser supports the capabilities that modern mobile web apps require. The main result from running a mobile browser through the Ringmark test suite is the number of the highest ring that the browser passed. The Ringmark test suite has been developed by Facebook and Bocoup. Ringmark test should not fail. What went wrong? Ringmark Test failed. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 64.0.3282.137 Channel: n/a OS Version: O-OS Flash Version: Device model number (e.g. G955W): J737V Android version: O-OS Chrome version : 64.0.3282.137
,
Mar 16 2018
,
Mar 16 2018
Tested the issue in Android and able to reproduce the issue as per the steps mentioned in original comment. Observed Ringmark Test failed Chrome versions tested: 65.0.3325.109(Stable), 67.0.3371.0(Canary) OS: Android 7.0.0 Android Devices: Samsung J7 Please navigate to below link for log's and video-- go/chrome-androidlogs/822132 This seems to be a Non-Regression as same behavior is seen since M58. Thanks!!
,
Mar 16 2018
Removing Blink>WebRTC for further triaging. I tested rng.io in a couple of devices and Chrome versions and WebRTC tests always passed. Other tests failed.
,
Mar 21 2018
,
Mar 23 2018
screenshot shows iframe sandboxing issues related to allowScript
,
Mar 27 2018
The iframe sandbox issue is a problem with the test, not with our support. It's checking the following: ``` assert(!c.contentWindow, "sandbox iframe is blocked") ``` That assertion is incorrect: the parent frame can reference the window (it couldn't otherwise do `postMessage()` for instance). Dropping the security component, can leave this open for the other failures.
,
Mar 28 2018
,
Mar 29 2018
Not sure what the video in c#3 is supposed to show. It doesn't even run rng.io. Even on desktop (Linux, chrome 66 beta), I see failures in ring 1 and 2: Ring 1: CSS Overflow Scrolling HTML5 Forms, Inputs (datetime missing?) Media Capture Input Ring 2: Animation timing CSS Element CSS Flexbox CSS3 Images CSS3 Images, Standard CSS Overflow Scrolling, Standard iframe SandBoxing Network Info For further triage, setting component to CSS to triage this first issue.
,
Mar 30 2018
,
Apr 23 2018
Ringmark is very outdated. Overflow scrolling is a -webkit- prefixes property which was removed in 2013. The flexbox test failures are for properties which may have been part of a spec ages ago. If you think there are failing tests which are real bugs, file them separately with references to recent specs. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by ruch...@samsung.com
, Mar 15 20183.8 MB
3.8 MB Download
153 KB
153 KB View Download
138 KB
138 KB View Download