Revision 31a51c70f74e23dc52f2033e552990a03f3166a9 authored by Mike Pennisi on 29 June 2018, 15:27:58 UTC, committed by Ms2ger on 02 July 2018, 14:31:05 UTC
Today, the return value of functions provided to the global `add_cleanup` function has no effect on the behavior of the test runner. An upcoming feature addition to testharness.js will cause the return value to influence test results [1]. Despite this, some existing tests have already been authored to return a value: the result of `document.exitFullScreen`. Although this is expected to be a Promise in conforming implementations, some browsers do not yet implement this functionality. To allow the new test harness feature to land without introducing harness errors, refactor existing tests to omit a return value. Additionally, use `Promise.prototype.catch` to avoid race conditions resulting from unhandled Promise rejections (which trigger a harness error in testharness.js today). [1] https://github.com/web-platform-tests/wpt/issues/6075
1 parent 21369c1
| File | Mode | Size |
|---|---|---|
| resources | ||
| META.yml | -rw-r--r-- | 43 bytes |
| compile_worker.js | -rw-r--r-- | 294 bytes |
| create_multiple_memory.worker.js | -rw-r--r-- | 538 bytes |
| incrementer.wasm | -rw-r--r-- | 46 bytes |
| wasm_idb_worker.js | -rw-r--r-- | 790 bytes |
| wasm_indexeddb_test.https.html | -rw-r--r-- | 586 bytes |
| wasm_indexeddb_test.js | -rw-r--r-- | 3.5 KB |
| wasm_local_iframe_test.html | -rw-r--r-- | 734 bytes |
| wasm_serialization_tests.html | -rw-r--r-- | 309 bytes |
| wasm_serialization_tests.js | -rw-r--r-- | 590 bytes |
| wasm_serialization_worker.js | -rw-r--r-- | 580 bytes |
| wasm_service_worker_test.https.html | -rw-r--r-- | 1021 bytes |
Computing file changes ...
