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
addRange-36.html
<!doctype html>
<title>Selection.addRange() tests</title>
<meta name="timeout" content="long">
<div id="log"></div>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="common.js"></script>
<script src="addRange.js"></script>
<script>
"use strict";
testAddRangeSubSet(36, 40);
testDiv.style.display = "none";
</script>
Computing file changes ...