ladybird/Libraries/LibWeb/Editing/CommandNames.cpp

/*
 * Copyright (c) 2024, Jelle Raaijmakers <jelle@ladybird.org>
 *
 * SPDX-License-Identifier: BSD-2-Clause
 */

#include <LibWeb/Editing/CommandNames.h>

namespace Web::Editing::CommandNames {

#define __ENUMERATE_COMMAND_NAME(name, command) \
    FlyString name = command##_fly_string;
ENUMERATE_COMMAND_NAMES
#undef __ENUMERATE_COMMAND_NAME

}
LibWeb: Implement document.execCommand("delete") To facilitate the implementation of "delete" and all associated algorithms, split off this piece of `Document` into a separate directory. This sets up the infrastructure for arbitrary commands to be supported. 2024-11-27 11:57:12 +01:00			`/*`
			`* Copyright (c) 2024, Jelle Raaijmakers <jelle@ladybird.org>`
			`*`
			`* SPDX-License-Identifier: BSD-2-Clause`
			`*/`

			`#include <LibWeb/Editing/CommandNames.h>`

			`namespace Web::Editing::CommandNames {`

LibWeb: Remove the initialize_strings methods We added these methods to propagate OOM errors at process startup, but we longer fret about these tiny OOM failures. Requiring that these init methods be called prohibits using these strings in processes that have not set up a MainThreadVM. So let's just remove them and initialize the strings in a sane manner. In doing so, this also standardizes how we initialize strings whose C++ variable name differs from their string value. Instead of special-casing these strings, we just include their string value in the x-macro list. 2025-01-11 14:07:41 -05:00			`#define __ENUMERATE_COMMAND_NAME(name, command) \`
			`FlyString name = command##_fly_string;`
LibWeb: Implement document.execCommand("delete") To facilitate the implementation of "delete" and all associated algorithms, split off this piece of `Document` into a separate directory. This sets up the infrastructure for arbitrary commands to be supported. 2024-11-27 11:57:12 +01:00			`ENUMERATE_COMMAND_NAMES`
			`#undef __ENUMERATE_COMMAND_NAME`

			`}`