1859853 - WritableStream write timing doesn't match with Blink/WebKit if start function is async

Status: RESOLVED WONTFIX

(Core :: DOM: Streams, defect, P3)

Description

[Kagami Rosylight 🏳️‍🌈🏳️‍⚧️ [:saschanaz] (they/them)]

new WritableStream({
  async start() {},
  async write(chunk) {
    console.log(chunk)
  }
}).getWriter().write('write');
Promise.resolve('promise').then(console.log)

Gecko: promise and then write
Blink/WebKit: write and then promise

But not sure why, shouldn't the write operation wait for start promise here?

Comment 1

[Kagami Rosylight 🏳️‍🌈🏳️‍⚧️ [:saschanaz] (they/them)]

Hmm.

WebKit: it just uses Promise.resolve() instead of "a promise resolved with" steps: https://searchfox.org/wubkat/rev/afcea26699c7f4b151758a203f76cd4fb5ef68fe/Source/WebCore/Modules/streams/WritableStreamInternals.js#596

Blink: Somehow start algorithms are made to always wrapped with Promise.resolve() which then is used directly with .then() on it.

So nobody is doing what the spec says. The reference implementation follows the Gecko behavior as expected.

(But I don't think the spec has a point, why make extra promise at all here?)

Comment 2

[Kagami Rosylight 🏳️‍🌈🏳️‍⚧️ [:saschanaz] (they/them)]

This is not our defect, closing while keeping the spec issue open.