- [ ] More concretely define differences in `fetch` - [ ] Better integration with WebIDL - [x] Make sure even if we don't have a `Window` interface, things get exposed in the equivalent global objects - [ ] https://github.com/WinterTC55/proposal-minimum-common-api/issues/63 - it is possible we have to do nothing because `FormData` is already present in `DedicatedWorkerGlobalScope`, where `HTMLFormElement` and `HTMLElement` are not present. - [ ] Define ESM integration - Come up with subset of resolution that is palatable to all runtimes (e.g relative imports between local files?) - Require that module specifiers must be URLs (and `import.meta.url` must be specified). - Figure out `fetch` interaction - can we reuse HTML spec text? - [ ] Actually publish a list of WPTs to run _Not a complete list._
fetchWindowinterface, things get exposed in the equivalent global objectsFormDataconstructor handle arguments in non-DOM runtimes? #63 - it is possible we have to do nothing becauseFormDatais already present inDedicatedWorkerGlobalScope, whereHTMLFormElementandHTMLElementare not present.import.meta.urlmust be specified).fetchinteraction - can we reuse HTML spec text?Not a complete list.