| OLD | NEW |
|---|
| (Empty) | |
| 1 This is a testharness.js-based test. |
| 2 PASS Service worker test setup |
| 3 PASS Aborting a WritableStream before it starts should cause the writer's unsett
led ready promise to reject |
| 4 PASS Aborting a WritableStream should cause the writer's fulfilled ready promise
to reset to a rejected one |
| 5 PASS abort() on a released writer rejects |
| 6 PASS Aborting a WritableStream immediately prevents future writes |
| 7 PASS Aborting a WritableStream prevents further writes after any that are in pro
gress |
| 8 PASS Fulfillment value of ws.abort() call must be undefined even if the underlyi
ng sink returns a non-undefined value |
| 9 PASS WritableStream if sink's abort throws, the promise returned by writer.abort
() rejects |
| 10 PASS WritableStream if sink's abort throws, the promise returned by ws.abort() r
ejects |
| 11 PASS WritableStream if sink's abort throws, for an abort performed during a writ
e, the promise returned by ws.abort() rejects |
| 12 PASS Aborting a WritableStream passes through the given reason |
| 13 PASS Aborting a WritableStream puts it in an errored state, with a TypeError as
the stored error |
| 14 PASS Aborting a WritableStream causes any outstanding write() promises to be rej
ected with a TypeError |
| 15 PASS Closing but then immediately aborting a WritableStream causes the stream to
error |
| 16 PASS Closing a WritableStream and aborting it while it closes causes the stream
to error |
| 17 PASS Aborting a WritableStream after it is closed is a no-op |
| 18 PASS WritableStream should NOT call underlying sink's close if no abort is suppl
ied (historical) |
| 19 PASS returning a thenable from abort() should work |
| 20 PASS .closed should not resolve before fulfilled write() |
| 21 PASS .closed should not resolve before rejected write(); write() error should ov
erwrite abort() error |
| 22 PASS writes should be satisfied in order when aborting |
| 23 PASS writes should be satisfied in order after rejected write when aborting |
| 24 PASS close() should use error from underlying write() on abort |
| 25 PASS underlying abort() should not be called until underlying write() completes |
| 26 PASS underlying abort() should not be called if underlying close() has started |
| 27 PASS if underlying close() has started and then rejects, the abort() and close()
promises should reject with the underlying close rejection reason |
| 28 PASS underlying abort() should be called while closing if underlying close() has
not started yet |
| 29 PASS writer close() promise should resolve before abort() promise |
| 30 PASS writer.ready should reject on controller error without waiting for underlyi
ng write |
| 31 FAIL writer.abort() while there is a pending write, and then finish the write wi
th rejection assert_array_equals: writePromise, abortPromise and writer.closed m
ust reject property 1, expected "abortPromise" but got "closed" |
| 32 FAIL writer.abort(), controller.error() while there is a pending write, and then
finish the write promise_test: Unhandled rejection with value: object "TypeErro
r: Cannot error a errored writable stream" |
| 33 PASS controller.error(), writer.abort() while there is a pending write, and then
finish the write |
| 34 PASS releaseLock() while aborting should reject the original closed promise |
| 35 PASS releaseLock() during delayed async abort() should create a new rejected clo
sed promise |
| 36 Harness: the test ran to completion. |
| 37 |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 2665073003:
Import wpt@cd5cce9780f84cee679919679b8199084ea96d54 (Closed)
