gecko-dev/testing/web-platform/tests/native-io
Anne van Kesteren 1d883303eb Bug 1631719 [wpt PR 23133] - *.any.js: explicitly list defaults, part 3, a=testonly
Automatic update from web-platform-tests
*.any.js: explicitly list defaults, part 3

*.any.js's META global no longer supports negation or the default feature making everything a bit easier as a result.

See https://github.com/web-platform-tests/rfcs/pull/52, #23117, and #23121.

Closes #23111.
--

wpt-commits: 96c7f0b57b704c94a7535d58009500ea94c02995
wpt-pr: 23133
2020-05-04 18:11:51 +00:00
..
close_async.tentative.https.any.js Bug 1630700 [wpt PR 23023] - Replace assert_precondition with assert_equals in native-io/, a=testonly 2020-04-28 11:30:43 +00:00
close_sync.tentative.https.any.js Bug 1631719 [wpt PR 23133] - *.any.js: explicitly list defaults, part 3, a=testonly 2020-05-04 18:11:51 +00:00
concurrent_io_async.tentative.https.any.js Bug 1630700 [wpt PR 23023] - Replace assert_precondition with assert_equals in native-io/, a=testonly 2020-04-28 11:30:43 +00:00
delete_async_basic.tentative.https.any.js
delete_sync_basic.tentative.https.any.js Bug 1631719 [wpt PR 23133] - *.any.js: explicitly list defaults, part 3, a=testonly 2020-05-04 18:11:51 +00:00
META.yml
open_getAll_async_basic.tentative.https.any.js
open_getAll_sync_basic.tentative.https.any.js Bug 1631719 [wpt PR 23133] - *.any.js: explicitly list defaults, part 3, a=testonly 2020-05-04 18:11:51 +00:00
read_write_async_basic.tentative.https.any.js
read_write_sync_basic.tentative.https.any.js Bug 1631719 [wpt PR 23133] - *.any.js: explicitly list defaults, part 3, a=testonly 2020-05-04 18:11:51 +00:00
README.md

This directory contains tests for the NativeIO API.

Note on the synchronous APIs

Chrome is currently working with developers to explore the performance implications of using NativeIO as an asynchronous Promise-based API from WebAssembly.

In order to assess the performance overhead, a baseline is needed. This baseline is a synchronous API that can be easily used to port existing database code to WebAssembly. The synchronous API is only exposed to dedicated workers.

Until our performance studies are concluded, Chrome has no plans of shipping the synchronous API. In other words, there are no plans of adding a new synchronous storage API to the Web Platform.