a3bfaf1f42
Automatic update from web-platform-tests Improve idlharness-ShadowRealm integration By exposing a fetch_spec() on globalThis in testharness-shadowrealm-inner, we no longer need to have IDL tests in separate files for ShadowRealm, as the regular idlharness.js will just run there. Delete all existing idlharness-shadowrealm.window.js files and incorporate them into their neighbouring idlharness.any.js files. It seems sufficient to run the IDL tests only in shadowrealm-in-window; repeating them in every ShadowRealm scope seems like overkill. -- Improve test message in idlharness This gets me every time. If we are testing that an interface is not exposed, we should be clear about that in the test message. -- Don't test namespaces in idlharness if not exposed Instead, if a namespace is not exposed, test that there is no global property of that name, similar to what we do with interfaces. -- wpt-commits: 67880a4eb83ca9aa732eec4b35a1971ff5bf37ff, 524e1e0643c9d42e74f0bec6092227738b605f76, 49980192b50a30cd8bbea9b6baab9ac191eb1eb7 wpt-pr: 49342
18 lines
414 B
JavaScript
18 lines
414 B
JavaScript
// META: script=/resources/WebIDLParser.js
|
|
// META: script=/resources/idlharness.js
|
|
// META: global=window,dedicatedworker,shadowrealm-in-window
|
|
|
|
"use strict";
|
|
|
|
idl_test(
|
|
['webidl'],
|
|
[],
|
|
idl_array => {
|
|
idl_array.add_objects({
|
|
DOMException: ['new DOMException()',
|
|
'new DOMException("my message")',
|
|
'new DOMException("my message", "myName")']
|
|
});
|
|
}
|
|
);
|