a document loading question:

https://html.spec.whatwg.org/multipage/document-lifecycle.html#read-ua-inline
step 3 assumes there is "response" from which URL can be obtained but "response" is not listed in the parameters.
step 4 initialize navigationParams params with newly created response but step 5 that creates document using these navigationParams seems to assume that response always has non-empty URL.

am I missing something or there is a bug that "Loading a document for inline content that doesn't have a DOM" should accept url?

streams question:

(async () => {
  let stream = new ReadableStream(
    {
      start(controller) {
          controller.enqueue(Promise.resolve(0)); // NOTE: enqueuing a promise
          controller.close();
      },
    },
  );
  for await (let item of stream) {
    console.log({ item });
  }
})();

(Streams are async iterable as of https://github.com/whatwg/streams/pull/980, though only FF has implemented as far as I know.)

Here, should the console.log be of 0 or of a Promise for 0? If I'm reading the various specs right, it should be a Promise. FF has it as an actual 0. The original conversation about async iterators which yield promises (in the iterator result object) decided that it should be considered a contract violation to do so - see slide 27 of https://docs.google.com/presentation/d/1U6PivKbFO0YgoFlrYB82MtXf1ofCp1xSVOODOvranBM/edit#slide=id.g223fba4116_0_196

this is really an edge case, so maybe the "contract violation" is fine? it's not like the language enforces that contract. but if the intent is that it should be a Promise for 0, that probably warrants a WPT