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.
51 lines
1.3 KiB
C++
51 lines
1.3 KiB
C++
/*
|
|
* Copyright (c) 2022, Andreas Kling <andreas@ladybird.org>
|
|
* Copyright (c) 2022, Sam Atkins <atkinssj@serenityos.org>
|
|
*
|
|
* SPDX-License-Identifier: BSD-2-Clause
|
|
*/
|
|
|
|
#include <LibWeb/Bindings/DOMPointPrototype.h>
|
|
#include <LibWeb/Bindings/Intrinsics.h>
|
|
#include <LibWeb/Geometry/DOMPoint.h>
|
|
|
|
namespace Web::Geometry {
|
|
|
|
JS_DEFINE_ALLOCATOR(DOMPoint);
|
|
|
|
JS::NonnullGCPtr<DOMPoint> DOMPoint::construct_impl(JS::Realm& realm, double x, double y, double z, double w)
|
|
{
|
|
return realm.create<DOMPoint>(realm, x, y, z, w);
|
|
}
|
|
|
|
JS::NonnullGCPtr<DOMPoint> DOMPoint::create(JS::Realm& realm)
|
|
{
|
|
return realm.create<DOMPoint>(realm);
|
|
}
|
|
|
|
DOMPoint::DOMPoint(JS::Realm& realm, double x, double y, double z, double w)
|
|
: DOMPointReadOnly(realm, x, y, z, w)
|
|
{
|
|
}
|
|
|
|
DOMPoint::DOMPoint(JS::Realm& realm)
|
|
: DOMPointReadOnly(realm)
|
|
{
|
|
}
|
|
|
|
// https://drafts.fxtf.org/geometry/#dom-dompoint-frompoint
|
|
JS::NonnullGCPtr<DOMPoint> DOMPoint::from_point(JS::VM& vm, DOMPointInit const& other)
|
|
{
|
|
// The fromPoint(other) static method on DOMPoint must create a DOMPoint from the dictionary other.
|
|
return construct_impl(*vm.current_realm(), other.x, other.y, other.z, other.w);
|
|
}
|
|
|
|
DOMPoint::~DOMPoint() = default;
|
|
|
|
void DOMPoint::initialize(JS::Realm& realm)
|
|
{
|
|
Base::initialize(realm);
|
|
WEB_SET_PROTOTYPE_FOR_INTERFACE(DOMPoint);
|
|
}
|
|
|
|
}
|