Revision 5e8eef740f9a79e5626fa41ef67a4b6284a6490b authored by Kouhei Ueno on 06 October 2017, 06:35:33 UTC, committed by Chromium WPT Sync on 06 October 2017, 06:35:33 UTC
Dynamic imports rely on url, nonce, and parser state to be attributed correctly. This CL updates ScheduledAction to plumb down the info as spec-ed via ScriptSourceCode. Test: LayoutTests/external/wpt/html/semantics/scripting-1/the-script-element/module/dynamic-import/no-propagate-nonce-setTimeout.html Bug: 711706 Change-Id: Iabb21f72d9cdafce502aa131773268ba20dd1648
1 parent 531cc81
silent-ignore.html
<!DOCTYPE html>
<html>
<head>
<meta charset='utf-8'/>
<title>Vibration API: test that calls to vibrate() are silently ignored when the device cannot vibrate</title>
<link rel='author' title='Robin Berjon' href='mailto:robin@berjon.com'/>
<link rel='help' href='http://www.w3.org/TR/vibration/#methods'/>
<meta name='flags' content='dom, no-vibrator'/>
<meta name='assert' content='If the device does not provide a vibration mechanism, or it is disabled, the user agent must silently ignore any invocations of the vibrate() method.'/>
</head>
<body>
<h1>Description</h1>
<p>
<strong>This test is only useful on devices that do not have vibration capability</strong>.
If your device supports vibration, then <strong>skip</strong> this test. An implementation
supporting this API but running on a device that cannot vibrate must silently ignore the
call (we test that it doesn't throw).
</p>
<div id='log'></div>
<script src='/resources/testharness.js'></script>
<script src='/resources/testharnessreport.js'></script>
<script>
if (undefined !== navigator.vibrate) {
test(function () {
assert_true(navigator.vibrate(1000), "vibrate() returns true when vibration is not supported");
}, "Calling vibrate returns true");
}
</script>
</body>
</html>
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...