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

Editorial: Update links in post-'resolve a module specifier' assertions #6031

Conversation

dandclark
Copy link
Contributor

@dandclark dandclark commented Oct 5, 2020

The explanatory text of the assertion in HostResolveImportedModule stating that resolve a module specifier must have been previously successful lists HostImportModuleDynamically as one of the places where resolve a module specifier would previously have succeeded. However, it's fetch() an import() module script graph, called by HostImportModuleDynamically, where resolve a module specifier is actually called. Update the assertion text to reference fetch() an import() module script graph directly.

The corresponding assertion in find the first parse error didn't have a link to where the prior resolve a module specifier call would occur, so add one.


/webappapis.html ( diff )

…ns to point to where the prior 'resolve a module specifier' occurred.
Copy link
Member

@domenic domenic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome, thanks!

@domenic domenic added clarification Standard could be clearer topic: script labels Oct 6, 2020
@domenic domenic merged commit 5e107e3 into whatwg:master Oct 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Standard could be clearer topic: script
Development

Successfully merging this pull request may close these issues.

None yet

2 participants