Stowage/ladybird
2
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-10-19 15:43:20 +00:00
Code Issues Projects Releases Packages Wiki Activity
ladybird/Userland/Libraries/LibWeb/DOM/AbortController.cpp

50 lines
1.4 KiB
C++
Raw Normal View History

LibWeb: Add initial support for AbortController and AbortSignal The DOM specification says that the primary use case for these is to give Promises abort semantics. It is also a prerequisite for Fetch, as it is used to make Fetch abortable. a
2021-09-02 02:12:49 +01:00
/*
* Copyright (c) 2021, Luke Wilde <lukew@serenityos.org>
*
* SPDX-License-Identifier: BSD-2-Clause
*/
LibWeb: Remove unecessary dependence on Window from DOM and WebIDL These classes only needed Window to get at its realm. Pass a realm directly to construct DOM and WebIDL classes. This change importantly removes the guarantee that a Document will always have a non-null Window object. Only Documents created by a BrowsingContext will have a non-null Window object. Documents created by for example, DocumentFragment, will not have a Window (soon). This incremental commit leaves some workarounds in place to keep other parts of the code building.
2022-09-25 16:15:49 -06:00
#include <LibWeb/Bindings/Intrinsics.h>
LibWeb: Add initial support for AbortController and AbortSignal The DOM specification says that the primary use case for these is to give Promises abort semantics. It is also a prerequisite for Fetch, as it is used to make Fetch abortable. a
2021-09-02 02:12:49 +01:00
#include <LibWeb/DOM/AbortController.h>
#include <LibWeb/DOM/AbortSignal.h>
namespace Web::DOM {
LibWeb: Remove unecessary dependence on Window from DOM and WebIDL These classes only needed Window to get at its realm. Pass a realm directly to construct DOM and WebIDL classes. This change importantly removes the guarantee that a Document will always have a non-null Window object. Only Documents created by a BrowsingContext will have a non-null Window object. Documents created by for example, DocumentFragment, will not have a Window (soon). This incremental commit leaves some workarounds in place to keep other parts of the code building.
2022-09-25 16:15:49 -06:00
JS::NonnullGCPtr<AbortController> AbortController::construct_impl(JS::Realm& realm)
LibWeb: Make AbortController GC-allocated
2022-09-02 14:59:27 +02:00
{
LibWeb: Remove unecessary dependence on Window from DOM and WebIDL These classes only needed Window to get at its realm. Pass a realm directly to construct DOM and WebIDL classes. This change importantly removes the guarantee that a Document will always have a non-null Window object. Only Documents created by a BrowsingContext will have a non-null Window object. Documents created by for example, DocumentFragment, will not have a Window (soon). This incremental commit leaves some workarounds in place to keep other parts of the code building.
2022-09-25 16:15:49 -06:00
auto signal = AbortSignal::construct_impl(realm);
LibJS+Everywhere: Propagate Cell::initialize errors from Heap::allocate Callers that are already in a fallible context will now TRY to allocate cells. Callers in infallible contexts get a FIXME.
2023-01-28 13:39:44 -05:00
return realm.heap().allocate<AbortController>(realm, realm, move(signal)).release_allocated_value_but_fixme_should_propagate_errors();
LibWeb: Make AbortController GC-allocated
2022-09-02 14:59:27 +02:00
}
LibWeb: Add initial support for AbortController and AbortSignal The DOM specification says that the primary use case for these is to give Promises abort semantics. It is also a prerequisite for Fetch, as it is used to make Fetch abortable. a
2021-09-02 02:12:49 +01:00
// https://dom.spec.whatwg.org/#dom-abortcontroller-abortcontroller
LibWeb: Remove unecessary dependence on Window from DOM and WebIDL These classes only needed Window to get at its realm. Pass a realm directly to construct DOM and WebIDL classes. This change importantly removes the guarantee that a Document will always have a non-null Window object. Only Documents created by a BrowsingContext will have a non-null Window object. Documents created by for example, DocumentFragment, will not have a Window (soon). This incremental commit leaves some workarounds in place to keep other parts of the code building.
2022-09-25 16:15:49 -06:00
AbortController::AbortController(JS::Realm& realm, JS::NonnullGCPtr<AbortSignal> signal)
: PlatformObject(realm)
LibWeb: Make AbortController GC-allocated
2022-09-02 14:59:27 +02:00
, m_signal(move(signal))
{
}
AbortController::~AbortController() = default;
LibJS+Everywhere: Allow Cell::initialize overrides to throw OOM errors Note that as of this commit, there aren't any such throwers, and the call site in Heap::allocate will drop exceptions on the floor. This commit only serves to change the declaration of the overrides, make sure they return an empty value, and to propagate OOM errors frm their base initialize invocations.
2023-01-28 12:33:35 -05:00
JS::ThrowCompletionOr<void> AbortController::initialize(JS::Realm& realm)
LibWeb: Move setting of Web object prototypes to initialize() This needs to happen before prototype/constructor intitialization can be made lazy. Otherwise, GC could run during the C++ constructor and try to collect the object currently being created.
2023-01-10 06:28:20 -05:00
{
LibJS+Everywhere: Allow Cell::initialize overrides to throw OOM errors Note that as of this commit, there aren't any such throwers, and the call site in Heap::allocate will drop exceptions on the floor. This commit only serves to change the declaration of the overrides, make sure they return an empty value, and to propagate OOM errors frm their base initialize invocations.
2023-01-28 12:33:35 -05:00
MUST_OR_THROW_OOM(Base::initialize(realm));
LibWeb: Move setting of Web object prototypes to initialize() This needs to happen before prototype/constructor intitialization can be made lazy. Otherwise, GC could run during the C++ constructor and try to collect the object currently being created.
2023-01-10 06:28:20 -05:00
set_prototype(&Bindings::ensure_web_prototype<Bindings::AbortControllerPrototype>(realm, "AbortController"));
LibJS+Everywhere: Allow Cell::initialize overrides to throw OOM errors Note that as of this commit, there aren't any such throwers, and the call site in Heap::allocate will drop exceptions on the floor. This commit only serves to change the declaration of the overrides, make sure they return an empty value, and to propagate OOM errors frm their base initialize invocations.
2023-01-28 12:33:35 -05:00
return {};
LibWeb: Move setting of Web object prototypes to initialize() This needs to happen before prototype/constructor intitialization can be made lazy. Otherwise, GC could run during the C++ constructor and try to collect the object currently being created.
2023-01-10 06:28:20 -05:00
}
LibWeb: Make AbortController GC-allocated
2022-09-02 14:59:27 +02:00
void AbortController::visit_edges(Cell::Visitor& visitor)
LibWeb: Add initial support for AbortController and AbortSignal The DOM specification says that the primary use case for these is to give Promises abort semantics. It is also a prerequisite for Fetch, as it is used to make Fetch abortable. a
2021-09-02 02:12:49 +01:00
{
LibWeb: Make AbortController GC-allocated
2022-09-02 14:59:27 +02:00
Base::visit_edges(visitor);
visitor.visit(m_signal.ptr());
LibWeb: Add initial support for AbortController and AbortSignal The DOM specification says that the primary use case for these is to give Promises abort semantics. It is also a prerequisite for Fetch, as it is used to make Fetch abortable. a
2021-09-02 02:12:49 +01:00
}
// https://dom.spec.whatwg.org/#dom-abortcontroller-abort
LibWeb: Add support for AbortSignal.reason
2021-12-10 20:05:12 +00:00
void AbortController::abort(JS::Value reason)
LibWeb: Add initial support for AbortController and AbortSignal The DOM specification says that the primary use case for these is to give Promises abort semantics. It is also a prerequisite for Fetch, as it is used to make Fetch abortable. a
2021-09-02 02:12:49 +01:00
{
LibWeb: Add support for AbortSignal.reason
2021-12-10 20:05:12 +00:00
// The abort(reason) method steps are to signal abort on this’s signal with reason if it is given.
m_signal->signal_abort(reason);
LibWeb: Add initial support for AbortController and AbortSignal The DOM specification says that the primary use case for these is to give Promises abort semantics. It is also a prerequisite for Fetch, as it is used to make Fetch abortable. a
2021-09-02 02:12:49 +01:00
}
}
Reference in a new issue Copy permalink