ladybird/Libraries/LibWeb/HTML/CustomElements/CustomElementReactionNames.cpp

/*
 * Copyright (c) 2023, Luke Wilde <lukew@serenityos.org>
 *
 * SPDX-License-Identifier: BSD-2-Clause
 */

#include <LibWeb/HTML/CustomElements/CustomElementReactionNames.h>

namespace Web::HTML::CustomElementReactionNames {

#define __ENUMERATE_CUSTOM_ELEMENT_REACTION_NAME(name) \
    FlyString name = #name##_fly_string;
ENUMERATE_CUSTOM_ELEMENT_REACTION_NAMES
#undef __ENUMERATE_CUSTOM_ELEMENT_REACTION_NAME

}
LibWeb: Introduce CustomElementRegistry and creating custom elements The main missing feature here is form associated custom elements. 2023-03-29 23:46:18 +01:00			`/*`
			`* Copyright (c) 2023, Luke Wilde <lukew@serenityos.org>`
			`*`
			`* SPDX-License-Identifier: BSD-2-Clause`
			`*/`

			`#include <LibWeb/HTML/CustomElements/CustomElementReactionNames.h>`

			`namespace Web::HTML::CustomElementReactionNames {`

			`#define __ENUMERATE_CUSTOM_ELEMENT_REACTION_NAME(name) \`
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			`FlyString name = #name##_fly_string;`
			`ENUMERATE_CUSTOM_ELEMENT_REACTION_NAMES`
LibWeb: Introduce CustomElementRegistry and creating custom elements The main missing feature here is form associated custom elements. 2023-03-29 23:46:18 +01:00			`#undef __ENUMERATE_CUSTOM_ELEMENT_REACTION_NAME`

			`}`