standard

Looking at sticky activation it seems to be calling current high resolution time without a global (that is needed in order to know the time origin).

It'd be good to pass along the global. (W or window, if I'm reading the algorithms correctly)

Web Packaging "comes in several layers":

• Bundled HTTP Exchanges (Web Bundles):
  https://datatracker.ietf.org/doc/html/draft-ietf-wpack-bundled-responses

  .wbn file extension = application/webbundle

• Signed HTTP Exchanges:
  https://tools.ietf.org/html/draft-yasskin-http-origin-signed-responses

  .sxg file extension = `application/signe

Problem

The " Build ESP32 QEMU and Run Tests" task of the "QEMU / ESP32" test seems to fail randomly. It failed on project-chip/connectedhomeip#2009 for me, then passed when retriggered.

Proposed Solution

Figure out why it fails randomly and fix. Sadly the logs CI provides don't include the src/transport/tests/test-suite.log file that should have includ

Presumably these should result in a network error. The current specification doesn't state anything and it's not tested either.

See the README for instructions on where to add tests. In the specification the "blob" case of https://fetch.spec.whatwg.org/#scheme-fetch needs updating to handle current URL’s blob URL entry being null.

Under point 6 of the list of steps to take to "ensure pre-insertion validity", as part of an attempt to implement a procedure involving the particular list of steps, I am having trouble unambiguously interpreting the following statement:

parent has an element child, child is a doctype, or child is non-null and a do

https://url.spec.whatwg.org/commit-snapshots/2ce49383db3506a3c1a527a775693af1100198ef/#host-parsing

5. If input is the empty string, then return 0.

IPv4 parser calls IPv4 number parser in Step 6.2:

2. Let result be the result of parsing part.       <-- call to IPv4 number parser
3. If result is failure, then return input.
4. If result[1] is tr