Commit 26ffbbc1 authored by haraken@chromium.org's avatar haraken@chromium.org

Replace ASSERT(!isScriptForbbiden()) in MicroTaskSuppression with RELEASE_ASSERT

We normally use RELEASE_ASSERT for checking !isScriptForbbiden() because executing
a script in places where script execution is not allowed can lead to security issues.

Review URL: https://codereview.chromium.org/1304103002

git-svn-id: svn://svn.chromium.org/blink/trunk@200984 bbb929c8-8fbe-4397-9dbb-9b2b20218538
parent 7daf7a89
......@@ -95,7 +95,7 @@ public:
: m_isolate(isolate)
#endif
{
ASSERT(!ScriptForbiddenScope::isScriptForbidden());
RELEASE_ASSERT(!ScriptForbiddenScope::isScriptForbidden());
#if ENABLE(ASSERT)
V8PerIsolateData::from(m_isolate)->incrementInternalScriptRecursionLevel();
#endif
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment