What example satisfies it? I tried many ways and none of them worked.

The rules for choosing a navigable

4. If currentDocument's opener policy's value is "same-origin" or "same-origin-plus-COEP", and currentDocument's origin is not same origin with currentDocument's relevant settings object's top-level origin, then:
   1. Set noopener to true.
   2. Set name to "_blank".
   3. Set windowType to "new with no opener".
      ...
5. Return chosen and windowType.

window open steps

13. Let targetNavigable and windowType be the result of applying the rules for choosing a navigable given target, sourceDocument's node navigable, and noopener.
14. If noopener is true or windowType is "new with no opener", then return null.

Hey, I have a question about this part of the Streams spec.

In the spec, there's this assertion during return():
https://streams.spec.whatwg.org/#rs-asynciterator

Assert: reader.[[readRequests]] is empty, as the async iterator machinery guarantees that any previous calls to next() have settled before this is called.

But it seems like this assumption can be broken if you call return() directly before the previous next() settles.

Here’s a minimal example:

let controller;
const stream = new ReadableStream({
  start(c) {
    controller = c;
  }
});

const iter = stream[Symbol.asyncIterator]();
let next1Promise = iter.next();
let next2Promise = iter.next();

controller.enqueue("Hello");

await next1Promise;

iter.return();  

This was originally raised in Node.js here:
https://github.com/nodejs/node/issues/57679

In this section of the Web IDL spec, should the return method call the asynchronous iterator return steps only after the previous next call has settled?

Or am I missing something?