9b79a686eb
The main motivation behind this is to remove JS specifics of the Realm from the implementation of the Heap. As a side effect of this change, this is a bit nicer to read than the previous approach, and in my opinion, also makes it a little more clear that this method is specific to a JavaScript Realm.
44 lines
1.5 KiB
C++
44 lines
1.5 KiB
C++
/*
|
|
* Copyright (c) 2023, Andrew Kaster <akaster@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#include <LibJS/Heap/Heap.h>
|
|
#include <LibJS/Runtime/Realm.h>
|
|
#include <LibWeb/Bindings/Intrinsics.h>
|
|
#include <LibWeb/Bindings/NavigationCurrentEntryChangeEventPrototype.h>
|
|
#include <LibWeb/HTML/NavigationCurrentEntryChangeEvent.h>
|
|
#include <LibWeb/HTML/NavigationHistoryEntry.h>
|
|
|
|
namespace Web::HTML {
|
|
|
|
JS_DEFINE_ALLOCATOR(NavigationCurrentEntryChangeEvent);
|
|
|
|
JS::NonnullGCPtr<NavigationCurrentEntryChangeEvent> NavigationCurrentEntryChangeEvent::construct_impl(JS::Realm& realm, FlyString const& event_name, NavigationCurrentEntryChangeEventInit const& event_init)
|
|
{
|
|
return realm.create<NavigationCurrentEntryChangeEvent>(realm, event_name, event_init);
|
|
}
|
|
|
|
NavigationCurrentEntryChangeEvent::NavigationCurrentEntryChangeEvent(JS::Realm& realm, FlyString const& event_name, NavigationCurrentEntryChangeEventInit const& event_init)
|
|
: DOM::Event(realm, event_name, event_init)
|
|
, m_navigation_type(event_init.navigation_type)
|
|
, m_from(*event_init.from)
|
|
{
|
|
}
|
|
|
|
NavigationCurrentEntryChangeEvent::~NavigationCurrentEntryChangeEvent() = default;
|
|
|
|
void NavigationCurrentEntryChangeEvent::initialize(JS::Realm& realm)
|
|
{
|
|
Base::initialize(realm);
|
|
WEB_SET_PROTOTYPE_FOR_INTERFACE(NavigationCurrentEntryChangeEvent);
|
|
}
|
|
|
|
void NavigationCurrentEntryChangeEvent::visit_edges(JS::Cell::Visitor& visitor)
|
|
{
|
|
Base::visit_edges(visitor);
|
|
visitor.visit(m_from);
|
|
}
|
|
|
|
}
|