1358fe85b0
In the cases where spec authors have us directly interact with promises in a task source context, we need to prepare the backup settings object stack as well as push an actual execution context to the JS VM.
31 lines
870 B
C++
31 lines
870 B
C++
/*
|
|
* Copyright (c) 2023, Tim Flynn <trflynn89@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <LibWeb/Forward.h>
|
|
|
|
namespace Web::HTML {
|
|
|
|
// When JS is run from outside the context of any user script, we currently do not have a running execution context.
|
|
// This results in a crash when we access VM::running_execution_context(). This is a spec issue. Until it is resolved,
|
|
// this is a workaround to temporarily push an execution context.
|
|
class TemporaryExecutionContext {
|
|
public:
|
|
enum class CallbacksEnabled {
|
|
No,
|
|
Yes,
|
|
};
|
|
|
|
explicit TemporaryExecutionContext(EnvironmentSettingsObject&, CallbacksEnabled = CallbacksEnabled::No);
|
|
~TemporaryExecutionContext();
|
|
|
|
private:
|
|
EnvironmentSettingsObject& m_environment_settings;
|
|
CallbacksEnabled m_callbacks_enabled { CallbacksEnabled::No };
|
|
};
|
|
|
|
}
|