forked from mirrors/gecko-dev
d79e8ec3f8
This removes `tentative` from Web Locks tests which all three engines are passing. A couple of exceptions from https://wpt.fyi/results/web-locks?label=experimental&label=master&aligned * clientids: The test follows the spec, I think this is a Chrome bug. (https://w3c.github.io/web-locks/#dom-lockmanager-request, the use of environment's id) * signal: A couple of WebKit failures because of lack of AbortSignal custom reason support. Differential Revision: https://phabricator.services.mozilla.com/D200477
14 lines
529 B
JavaScript
14 lines
529 B
JavaScript
// META: title=Web Locks API: API requires secure context
|
|
// META: global=window,dedicatedworker,sharedworker,serviceworker
|
|
|
|
'use strict';
|
|
|
|
test(t => {
|
|
assert_true(self.isSecureContext);
|
|
assert_idl_attribute(navigator, 'locks',
|
|
'navigator.locks exists in secure context');
|
|
assert_true('LockManager' in self,
|
|
'LockManager is present in secure contexts');
|
|
assert_true('Lock' in self,
|
|
'Lock interface is present in secure contexts');
|
|
}, 'API presence in secure contexts');
|