Re: [whatwg/streams] Resolving promises with byte sequences results in UB (Issue #1178) from Matthew Gaudet on 2021-10-20 (public-webapps-github@w3.org from October 2021)

From: Matthew Gaudet <notifications@github.com>
Date: Wed, 20 Oct 2021 06:33:15 -0700
To: whatwg/streams <streams@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/streams/issues/1178/947672330@github.com>

(this might just be echoing @ricea above) 

I think this bug is even more general: I've got a prototype implementation of streams that uses the promise semantics, and [even without Fetch / Byte streams complications, it's still vulnerable to `Object.prototype.then`](https://phabricator.services.mozilla.com/D128950), because of the WebIDL resolution semantics. Essentially, the spec as written today shouldn't pass the simplified test case or response-stream-with-broken-then.any.js.

Chrome passes because they are still implementing the `forAuthorCode` bool workaround. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/streams/issues/1178#issuecomment-947672330

Received on Wednesday, 20 October 2021 13:33:28 UTC