Resolve ready and finished promises asynchronously

third_party/WebKit/Source/bindings/core/v8/ScriptPromiseProperty.h

Index: third_party/WebKit/Source/bindings/core/v8/ScriptPromiseProperty.h
diff --git a/third_party/WebKit/Source/bindings/core/v8/ScriptPromiseProperty.h b/third_party/WebKit/Source/bindings/core/v8/ScriptPromiseProperty.h
index e3e17bae21504b4da809cb2538d1cfc21d806976..f9791198c401a3a8cea87578cc7b0af8e79c9933 100644
--- a/third_party/WebKit/Source/bindings/core/v8/ScriptPromiseProperty.h
+++ b/third_party/WebKit/Source/bindings/core/v8/ScriptPromiseProperty.h
@@ -105,6 +105,7 @@ void ScriptPromiseProperty<HolderType, ResolvedType, RejectedType>::resolve(
     NOTREACHED();
     return;
   }
+  DCHECK(!ScriptForbiddenScope::isScriptForbidden());

[esprehn, 2017/01/06 21:10:25]

We usually RELEASE_ASSERT/CHECK this instead so it doesn't let security bugs
through.

[adithyas, 2017/01/06 21:33:41]

I plan on adding a RELEASE_ASSERT in a different patch. I added the DCHECK as a
regression test, a few of the web-animation-api/ and animation/ layout tests
fail with this added in (if the promises are resolved synchronously).

Also, the execution context checks are right below this line :)

   if (!getExecutionContext() || getExecutionContext()->isContextDestroyed())
     return;
   m_resolved = value;