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

Specify which settings object is used for dynamic import #3700

Merged
merged 3 commits into from
May 22, 2018

Conversation

nhiroki
Copy link
Contributor

@nhiroki nhiroki commented May 22, 2018

This patch makes the HostImportModuleDynamically algorithm use
referencing script's settings object, that is, an environment
settings object.

Before this patch, the algorithm uses an unspecified settings object.

cc: @nyaxt


/acknowledgements.html ( diff )
/webappapis.html ( diff )

This patch makes the HostImportModuleDynamically algorithm use
referencing script's settings object, that is, an environment
settings object.

Before this patch, the algorithm uses an unspecified settings object.
Copy link
Member

@nyaxt nyaxt left a comment

Choose a reason for hiding this comment

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

Please add yourself to the list of contributors

@nhiroki
Copy link
Contributor Author

nhiroki commented May 22, 2018

@nyaxt Done

@nhiroki
Copy link
Contributor Author

nhiroki commented May 22, 2018

@nyaxt My previous comment meant "Participant Agreement". I also added my name to the contributors in Acknowledgements :)

source Outdated
<li><p><span>Fetch a module script graph</span> given <var>url</var>, <var>referencing
script</var>'s <span>settings object</span>, "<code data-x="">script</code>", and
<var>options</var>. Wait until the algorithm asynchronously completes with <var>result</var>.
</p></li>
Copy link
Member

Choose a reason for hiding this comment

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

Nit: this linebreak adds an extra space after the period. Instead, please linebreak before the <var>

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

Successfully merging this pull request may close these issues.

3 participants