Name Description Size
.htaccess 107
accesskey.js Function that sends an accesskey using the proper key combination depending on the browser and OS. This needs that the test imports the following scripts: <script src="/resources/testdriver.js"></script> <script src="/resources/testdriver-actions.js"></script> <script src="/resources/testdriver-vendor.js"></script> 1233
blank.html Blank Page 379
channel.sub.js Cache of WebSocket instances per channel For reading there can only be one channel with each UUID, so we just have a simple map of {uuid: WebSocket}. The socket can be closed when the channel is closed. For writing there can be many channels for each uuid. Those can share a websocket (within a specific global), so we have a map of {uuid: [WebSocket, count]}. Count is incremented when a channel is opened with a given uuid, and decremented when its closed. When the count reaches zero we can close the underlying socket. 39120
check-layout-th.js 10271
check-layout.js 11392
idlharness-shadowrealm.js idl_test_shadowrealm is a promise_test wrapper that handles the fetching of the IDL, and running the code in a `ShadowRealm`, avoiding repetitive boilerplate. @see @param {String[]} srcs Spec name(s) for source idl files (fetched from /interfaces/{name}.idl). @param {String[]} deps Spec name(s) for dependency idl files (fetched from /interfaces/{name}.idl). Order is important - dependencies from each source will only be included if they're already know to be a dependency (i.e. have already been seen). 2564
idlharness.js For user documentation see docs/_writing-tests/ 145156
idlharness.js.headers 73
META.yml 33 # Resources 557
sriharness.js 7936
SVGAnimationTestCase-testharness.js 3715
test-only-api.js Whether the browser is Chromium-based with MojoJS enabled 932
test-only-api.js.headers 73
test-only-api.m.js Whether the browser is Chromium-based with MojoJS enabled 280
test-only-api.m.js.headers 73
testdriver-actions.js @class Builder for creating a sequence of actions The actions are dispatched once :js:func:`test_driver.Actions.send` is called. This returns a promise which resolves once the actions are complete. The other methods on :js:class:`test_driver.Actions` object are used to build the sequence of actions that will be sent. These return the `Actions` object itself, so the actions sequence can be constructed by chaining method calls. Internally :js:func:`test_driver.Actions.send` invokes :js:func:`test_driver.action_sequence`. @example let text_box = document.getElementById("text"); let actions = new test_driver.Actions() .pointerMove(0, 0, {origin: text_box}) .pointerDown() .pointerUp() .addTick() .keyDown("p") .keyUp("p"); await actions.send(); @param {number} [defaultTickDuration] - The default duration of a tick. Be default this is set ot 16ms, which is one frame time based on 60Hz display. 18833
testdriver-vendor.js 0
testdriver-vendor.js.headers 73
testdriver.js @namespace {test_driver} 56739
testdriver.js.headers 73
testharness.js global self 185667
testharness.js.headers 73
testharnessreport.js global add_completion_callback 1231
testharnessreport.js.headers 73