Okay, so the earlier test 'closing the writable side should reject if a parallel transformer.cancel() throws' works because that hits TransformStreamDefaultSourceCancelAlgorithm step 7.2.3, but this failing test never fails because when cancelPromise is resolved the writable stream's start promise is somehow still not resolved and thus hasn't called FinishErroring. But not sure how cancel promise responds first before start promise? I also commented on the issue.
Bug 1856103 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Okay, so the earlier test 'closing the writable side should reject if a parallel transformer.cancel() throws' works because that hits TransformStreamDefaultSourceCancelAlgorithm step 7.2.3, but this failing test never throws because when cancelPromise is resolved the writable stream's start promise is somehow still not resolved and thus hasn't called FinishErroring. But not sure how cancel promise responds first before start promise? I also commented on the issue.
Okay, so the earlier test 'closing the writable side should reject if a parallel transformer.cancel() throws' works because that hits TransformStreamDefaultSourceCancelAlgorithm step 7.2.3, but this failing test never throws because when cancelPromise is resolved, the writable stream's start promise is somehow still not resolved and thus hasn't called FinishErroring. But not sure how cancel promise responds first before start promise? I also commented on the issue.
Okay, so the earlier test 'closing the writable side should reject if a parallel transformer.cancel() throws' works because that hits TransformStreamDefaultSourceCancelAlgorithm step 7.2.3, but this failing test never throws because when cancelPromise is resolved, [the writable stream's start promise](https://searchfox.org/mozilla-central/rev/0ba4632ee85679a1ccaf652df79c971fa7e9b9f7/dom/streams/WritableStreamDefaultController.cpp#187-192) is somehow still not resolved and thus hasn't called FinishErroring. But not sure how cancel promise responds first before start promise? I also commented on the issue.
Okay, so the earlier test 'closing the writable side should reject if a parallel transformer.cancel() throws' works because that hits TransformStreamDefaultSourceCancelAlgorithm step 7.2.3, but this failing test never throws because when cancelPromise is resolved, [the writable stream's start promise](https://searchfox.org/mozilla-central/rev/0ba4632ee85679a1ccaf652df79c971fa7e9b9f7/dom/streams/WritableStreamDefaultController.cpp#187-192) is somehow still not resolved and thus hasn't called [FinishErroring](https://searchfox.org/mozilla-central/rev/0ba4632ee85679a1ccaf652df79c971fa7e9b9f7/dom/streams/WritableStream.cpp#113). But not sure how cancel promise responds first before start promise? I also commented on the issue.