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

48 lines
1.3 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: Make factory method of DOM::AbortController fallible
2023-02-14 20:45:54 +01:00
WebIDL::ExceptionOr<JS::NonnullGCPtr<AbortController>> AbortController::construct_impl(JS::Realm& realm)
LibWeb: Make AbortController GC-allocated
2022-09-02 14:59:27 +02:00
{
LibWeb: Make factory method of DOM::AbortSignal fallible
2023-02-14 21:02:46 +01:00
auto signal = TRY(AbortSignal::construct_impl(realm));
LibJS: Make Heap::allocate<T>() infallible Stop worrying about tiny OOMs. Work towards #20449. While going through these, I also changed the function signature in many places where returning ThrowCompletionOr<T> is no longer necessary.
2023-08-13 13:05:26 +02:00
return realm.heap().allocate<AbortController>(realm, realm, move(signal));
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: Make Cell::initialize() return void Stop worrying about tiny OOMs. Work towards #20405
2023-08-07 08:41:28 +02:00
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: Make Cell::initialize() return void Stop worrying about tiny OOMs. Work towards #20405
2023-08-07 08:41:28 +02:00
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"));
}
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);
LibWeb/LibJS: Avoid GC visit of raw pointers where possible This is mostly motivated for aesthetics, but also helps avoid some null checks when we have a NonnullGCPtr<T> or in some cases a T&.
2023-11-19 16:18:00 +13:00
visitor.visit(m_signal);
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