Revision 61d3da36e6cb16e4d4b9375518b0ae00308ee92a authored by Nicolas Pena on 25 April 2018, 18:35:25 UTC, committed by Blink WPT Bot on 25 April 2018, 18:53:19 UTC
This CL changes the webtiming-resolution to test that resolution is
larger than 10 microseconds, instead of testing for a specific value.
This allows the test to no longer be flaky and to be moved to wpt.
The webtiming-ssl test is moved to WPT, using an https connection to
ensure that secureConnectionStart is correctly defined.
Bug: chromium:801341
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: I4d31faa08d00251098f3dc648c794d80bbcc2f22
Reviewed-on: https://chromium-review.googlesource.com/867310
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553666}
1 parent 3a0a2e4
deviceorientationabsoluteevent.html
<!DOCTYPE html>
<html>
<head>
<title>DeviceOrientationEvent attributes should be fired properly</title>
<meta charset='utf-8'>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
</head>
<body>
<p>If an implementation can never provide absolute orientation information, the event should be fired with the alpha, beta and gamma attributes set to null.</p>
<div id="log"></div>
<script>
var t = async_test("deviceorientationabsolute event fires");
var run = false;
window.addEventListener("deviceorientationabsolute", function(e) {
if (!run) {
run = true;
t.step(function () {
assert_equals(e.type, "deviceorientationabsolute", "type is set to \"deviceorientationabsolute\"");
assert_equals(e.alpha, null, "alpha is set to null");
assert_equals(e.beta, null, "beta is set to null");
assert_equals(e.gamma, null, "gamma is set to null");
assert_false(e.absolute, "absolute is set to false");
});
t.done();
}
}, false);
</script>
</body>
</html>
Computing file changes ...
