Stowage/ladybird
2
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-10-30 21:01:00 +00:00
Code Issues Projects Releases Packages Wiki Activity
ladybird/Libraries/LibWeb/HTML/DataTransfer.h

94 lines
3.2 KiB
C
Raw Normal View History

LibWeb: Add an empty DataTransfer IDL implementation This does not implement any of the IDL methods, but GitHub requires the interface exists to upload files via an <input type="file"> element. Their JS handles uploads via this element and via drag-and-drop in one function, and check if the uploaded file is `instanceof DataTransfer` to decide how to handle it.
2024-03-13 15:35:39 -04:00
/*
* Copyright (c) 2024, Tim Flynn <trflynn89@serenityos.org>
*
* SPDX-License-Identifier: BSD-2-Clause
*/
#pragma once
#include <LibJS/Forward.h>
#include <LibWeb/Bindings/PlatformObject.h>
LibWeb: Implement the DataTransfer effect attributes
2024-08-16 13:40:56 -04:00
#include <LibWeb/HTML/DragDataStore.h>
LibWeb: Add an empty DataTransfer IDL implementation This does not implement any of the IDL methods, but GitHub requires the interface exists to upload files via an <input type="file"> element. Their JS handles uploads via this element and via drag-and-drop in one function, and check if the uploaded file is `instanceof DataTransfer` to decide how to handle it.
2024-03-13 15:35:39 -04:00
namespace Web::HTML {
LibWeb: Implement the DataTransfer effect attributes
2024-08-16 13:40:56 -04:00
#define ENUMERATE_DATA_TRANSFER_EFFECTS \
__ENUMERATE_DATA_TRANSFER_EFFECT(none) \
__ENUMERATE_DATA_TRANSFER_EFFECT(copy) \
__ENUMERATE_DATA_TRANSFER_EFFECT(copyLink) \
__ENUMERATE_DATA_TRANSFER_EFFECT(copyMove) \
__ENUMERATE_DATA_TRANSFER_EFFECT(link) \
__ENUMERATE_DATA_TRANSFER_EFFECT(linkMove) \
__ENUMERATE_DATA_TRANSFER_EFFECT(move) \
__ENUMERATE_DATA_TRANSFER_EFFECT(all) \
__ENUMERATE_DATA_TRANSFER_EFFECT(uninitialized)
namespace DataTransferEffect {
#define __ENUMERATE_DATA_TRANSFER_EFFECT(name) extern FlyString name;
ENUMERATE_DATA_TRANSFER_EFFECTS
#undef __ENUMERATE_DATA_TRANSFER_EFFECT
}
// https://html.spec.whatwg.org/multipage/dnd.html#the-datatransfer-interface
LibWeb: Add an empty DataTransfer IDL implementation This does not implement any of the IDL methods, but GitHub requires the interface exists to upload files via an <input type="file"> element. Their JS handles uploads via this element and via drag-and-drop in one function, and check if the uploaded file is `instanceof DataTransfer` to decide how to handle it.
2024-03-13 15:35:39 -04:00
class DataTransfer : public Bindings::PlatformObject {
WEB_PLATFORM_OBJECT(DataTransfer, Bindings::PlatformObject);
LibGC+Everywhere: Factor out a LibGC from LibJS Resulting in a massive rename across almost everywhere! Alongside the namespace change, we now have the following names: * JS::NonnullGCPtr -> GC::Ref * JS::GCPtr -> GC::Ptr * JS::HeapFunction -> GC::Function * JS::CellImpl -> GC::Cell * JS::Handle -> GC::Root
2024-11-15 04:01:23 +13:00
GC_DECLARE_ALLOCATOR(DataTransfer);
LibWeb: Add an empty DataTransfer IDL implementation This does not implement any of the IDL methods, but GitHub requires the interface exists to upload files via an <input type="file"> element. Their JS handles uploads via this element and via drag-and-drop in one function, and check if the uploaded file is `instanceof DataTransfer` to decide how to handle it.
2024-03-13 15:35:39 -04:00
public:
LibGC+Everywhere: Factor out a LibGC from LibJS Resulting in a massive rename across almost everywhere! Alongside the namespace change, we now have the following names: * JS::NonnullGCPtr -> GC::Ref * JS::GCPtr -> GC::Ptr * JS::HeapFunction -> GC::Function * JS::CellImpl -> GC::Cell * JS::Handle -> GC::Root
2024-11-15 04:01:23 +13:00
static GC::Ref<DataTransfer> create(JS::Realm&, NonnullRefPtr<DragDataStore>);
static GC::Ref<DataTransfer> construct_impl(JS::Realm&);
LibWeb: Add an empty DataTransfer IDL implementation This does not implement any of the IDL methods, but GitHub requires the interface exists to upload files via an <input type="file"> element. Their JS handles uploads via this element and via drag-and-drop in one function, and check if the uploaded file is `instanceof DataTransfer` to decide how to handle it.
2024-03-13 15:35:39 -04:00
virtual ~DataTransfer() override;
LibWeb: Implement the DataTransfer effect attributes
2024-08-16 13:40:56 -04:00
FlyString const& drop_effect() const { return m_drop_effect; }
void set_drop_effect(String const&);
void set_drop_effect(FlyString);
FlyString const& effect_allowed() const { return m_effect_allowed; }
void set_effect_allowed(String const&);
void set_effect_allowed(FlyString);
void set_effect_allowed_internal(FlyString);
LibGC+Everywhere: Factor out a LibGC from LibJS Resulting in a massive rename across almost everywhere! Alongside the namespace change, we now have the following names: * JS::NonnullGCPtr -> GC::Ref * JS::GCPtr -> GC::Ptr * JS::HeapFunction -> GC::Function * JS::CellImpl -> GC::Cell * JS::Handle -> GC::Root
2024-11-15 04:01:23 +13:00
GC::Ref<DataTransferItemList> items();
LibWeb: Implement the DataTransfer items attribute
2024-08-20 18:44:22 -04:00
LibWeb: Implement the DataTransfer types attribute
2024-08-17 14:23:13 -04:00
ReadonlySpan<String> types() const;
LibWeb: Implement DataTransfer.prototype.getData() This is used by Google Lens. It will always return the empty string when dragging an image onto the Google Lens search field.
2024-08-20 18:29:00 -04:00
String get_data(String const& format) const;
LibGC+Everywhere: Factor out a LibGC from LibJS Resulting in a massive rename across almost everywhere! Alongside the namespace change, we now have the following names: * JS::NonnullGCPtr -> GC::Ref * JS::GCPtr -> GC::Ptr * JS::HeapFunction -> GC::Function * JS::CellImpl -> GC::Cell * JS::Handle -> GC::Root
2024-11-15 04:01:23 +13:00
GC::Ref<FileAPI::FileList> files() const;
LibWeb: Implement the DataTransfer files attribute
2024-08-17 14:44:26 -04:00
LibWeb: Implement DataTransferItemList.prototype.add()
2024-08-21 09:35:25 -04:00
Optional<DragDataStore::Mode> mode() const;
LibWeb: Implement the DataTransfer types attribute
2024-08-17 14:23:13 -04:00
void disassociate_with_drag_data_store();
LibWeb: Implement the DataTransfer effect attributes
2024-08-16 13:40:56 -04:00
LibGC+Everywhere: Factor out a LibGC from LibJS Resulting in a massive rename across almost everywhere! Alongside the namespace change, we now have the following names: * JS::NonnullGCPtr -> GC::Ref * JS::GCPtr -> GC::Ptr * JS::HeapFunction -> GC::Function * JS::CellImpl -> GC::Cell * JS::Handle -> GC::Root
2024-11-15 04:01:23 +13:00
GC::Ref<DataTransferItem> add_item(DragDataStoreItem item);
LibWeb: Implement DataTransferItemList.prototype.add()
2024-08-21 09:35:25 -04:00
bool contains_item_with_type(DragDataStoreItem::Kind, String const& type) const;
LibGC+Everywhere: Factor out a LibGC from LibJS Resulting in a massive rename across almost everywhere! Alongside the namespace change, we now have the following names: * JS::NonnullGCPtr -> GC::Ref * JS::GCPtr -> GC::Ptr * JS::HeapFunction -> GC::Function * JS::CellImpl -> GC::Cell * JS::Handle -> GC::Root
2024-11-15 04:01:23 +13:00
GC::Ref<DataTransferItem> item(size_t index) const;
LibWeb: Implement the DataTransferItem kind and type attributes
2024-08-21 10:24:45 -04:00
DragDataStoreItem const& drag_data(size_t index) const;
LibWeb: Implement the DataTransferItemList length attribute
2024-08-21 09:45:04 -04:00
size_t length() const;
LibWeb: Implement DataTransferItemList.prototype.add()
2024-08-21 09:35:25 -04:00
LibWeb: Add an empty DataTransfer IDL implementation This does not implement any of the IDL methods, but GitHub requires the interface exists to upload files via an <input type="file"> element. Their JS handles uploads via this element and via drag-and-drop in one function, and check if the uploaded file is `instanceof DataTransfer` to decide how to handle it.
2024-03-13 15:35:39 -04:00
private:
LibWeb: Implement separate DataTransfer factories for IDL / internal use The IDL constructor has to take separate steps than a DataTransfer that is internally constructed. Notably, an IDL-created object has its own drag data store, and that store is placed in a read-write mode.
2024-08-21 06:50:22 -04:00
DataTransfer(JS::Realm&, NonnullRefPtr<DragDataStore>);
LibWeb: Add an empty DataTransfer IDL implementation This does not implement any of the IDL methods, but GitHub requires the interface exists to upload files via an <input type="file"> element. Their JS handles uploads via this element and via drag-and-drop in one function, and check if the uploaded file is `instanceof DataTransfer` to decide how to handle it.
2024-03-13 15:35:39 -04:00
virtual void initialize(JS::Realm&) override;
LibWeb: Implement the DataTransfer items attribute
2024-08-20 18:44:22 -04:00
virtual void visit_edges(JS::Cell::Visitor&) override;
LibWeb: Implement the DataTransfer effect attributes
2024-08-16 13:40:56 -04:00
LibWeb: Implement the DataTransfer types attribute
2024-08-17 14:23:13 -04:00
void update_data_transfer_types_list();
LibWeb: Implement the DataTransfer effect attributes
2024-08-16 13:40:56 -04:00
// https://html.spec.whatwg.org/multipage/dnd.html#dom-datatransfer-dropeffect
FlyString m_drop_effect { DataTransferEffect::none };
// https://html.spec.whatwg.org/multipage/dnd.html#dom-datatransfer-effectallowed
FlyString m_effect_allowed { DataTransferEffect::none };
LibWeb: Implement the DataTransfer items attribute
2024-08-20 18:44:22 -04:00
// https://html.spec.whatwg.org/multipage/dnd.html#dom-datatransfer-items
LibGC+Everywhere: Factor out a LibGC from LibJS Resulting in a massive rename across almost everywhere! Alongside the namespace change, we now have the following names: * JS::NonnullGCPtr -> GC::Ref * JS::GCPtr -> GC::Ptr * JS::HeapFunction -> GC::Function * JS::CellImpl -> GC::Cell * JS::Handle -> GC::Root
2024-11-15 04:01:23 +13:00
GC::Ptr<DataTransferItemList> m_items;
Vector<GC::Ref<DataTransferItem>> m_item_list;
LibWeb: Implement the DataTransfer items attribute
2024-08-20 18:44:22 -04:00
LibWeb: Implement the DataTransfer types attribute
2024-08-17 14:23:13 -04:00
// https://html.spec.whatwg.org/multipage/dnd.html#concept-datatransfer-types
Vector<String> m_types;
LibWeb: Implement the DataTransfer effect attributes
2024-08-16 13:40:56 -04:00
// https://html.spec.whatwg.org/multipage/dnd.html#the-datatransfer-interface:drag-data-store-3
LibWeb: Make the drag data store reference counted Ownership of the drag data store is a bit weird. In a normal drag-and- drop operation, the DragAndDropEventHandler owns the store. When events are fired for the operation, the DataTransfer object assigned to those events are "associated" with the store. We currently represent that with an Optional<DragDataStore&>. However, it's also possible to create DataTransfer objects from scripts. Those objects create their own drag data store. This puts DataTransfer in a weird situation where it may own a store or just reference one. Rather than coming up with something like Variant<DDS, DDS&> or using MaybeOwned<DDS> here, we can get by with just making the store reference counted.
2024-08-21 06:39:02 -04:00
RefPtr<DragDataStore> m_associated_drag_data_store;
LibWeb: Add an empty DataTransfer IDL implementation This does not implement any of the IDL methods, but GitHub requires the interface exists to upload files via an <input type="file"> element. Their JS handles uploads via this element and via drag-and-drop in one function, and check if the uploaded file is `instanceof DataTransfer` to decide how to handle it.
2024-03-13 15:35:39 -04:00
};
}
Reference in a new issue Copy permalink