Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Undeclared "destination" in "fetch an external module script graph" #8110

Closed
nicolo-ribaudo opened this issue Jul 17, 2022 · 0 comments · Fixed by #8120
Closed

Undeclared "destination" in "fetch an external module script graph" #8110

nicolo-ribaudo opened this issue Jul 17, 2022 · 0 comments · Fixed by #8120

Comments

@nicolo-ribaudo
Copy link
Contributor

https://html.spec.whatwg.org/commit-snapshots/5be9e6255d7b6f3b3ab1754b716cc1bab579191d/#fetching-scripts

To fetch an external module script graph given a url, a settings object, and some options, run these steps. The algorithm will asynchronously complete with either null (on failure) or a module script (on success).

  1. Fetch a single module script given url, settings object, "script", options, settings object, "client", and with the top-level module fetch flag set. If the caller of this algorithm specified custom perform the fetch steps, pass those along as well. Wait until the algorithm asynchronously completes with result.
  2. If result is null, asynchronously complete this algorithm with null, and return.
  3. Let visited set be « (url, "javascript") ».
  4. Fetch the descendants of and link result given settings object, destination, and visited set. When this asynchronously completes with final result, asynchronously complete this algorithm with final result.

The destination variable used at step 4 seems to be undeclared, should it be "script"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

1 participant