You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The purpose of this patch is to nail down how HTML would
adjust to the needs of top-level await. The relevant change is,
the module.Evaluate() method will return a Promise that resolves
when the module is ready, and this will be passed to
FinishDynamicImport to wait on before resolving the Promise it returns.
It doesn't seem like anyone else needs to wait for a module script
to "finish" evaluating besides dynamic import.
This PR is just a sketch, not to be landed. Top-level await should
reach stage 3 before this change lands.
The PR where Evaluate returns a Promise is
guybedford/proposal-top-level-await#1
<li><p><span>Prepare to run script</span> given <var>settings</var>.</p></li>
87763
87763
87764
-
<li><p>Let <var>evaluationStatus</var> be null.</p></li>
87765
-
87766
87764
<li><p>If <var>script</var>'s <span data-x="concept-script-error-to-rethrow">error to
87767
-
rethrow</span> is not null, then set <var>evaluationStatus</var> to Completion { [[Type]]: throw,
87768
-
[[Value]]: <var>script</var>'s <span data-x="concept-script-error-to-rethrow">error to
87769
-
rethrow</span>, [[Target]]: empty }.</p></li>
87765
+
rethrow</span> is not null, then let <var>evaluationPromise</var> be a promise rejected with <var>script</var>'s <span data-x="concept-script-error-to-rethrow">error to
0 commit comments