2c3531ab78
This change also removes as much direct use of JS::Promise in LibWeb as possible. When specs refer to `Promise<T>` they should be assumed to be referring to the WebIDL Promise type, not the JS::Promise type. The one exception is the HostPromiseRejectionTracker hook on the JS VM. This facility and its associated sets and events are intended to expose the exact opaque object handles that were rejected to author code. This is not possible with the WebIDL Promise type, so we have to use JS::Promise or JS::Object to hold onto the promises. It also exposes which specs need some updates in the area of promises. WebDriver stands out in this regard. WebAudio could use some more cross-references to WebIDL as well to clarify things.
32 lines
917 B
C++
32 lines
917 B
C++
/*
|
|
* Copyright (c) 2023, Tim Flynn <trflynn89@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#pragma once
|
|
|
|
#include <LibJS/Heap/GCPtr.h>
|
|
#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:
|
|
JS::NonnullGCPtr<EnvironmentSettingsObject> m_environment_settings;
|
|
CallbacksEnabled m_callbacks_enabled { CallbacksEnabled::No };
|
|
};
|
|
|
|
}
|