Stowage/ladybird
2
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-11-04 07:10:57 +00:00
Code Issues Projects Releases Packages Wiki Activity
ladybird/Userland/Libraries/LibWeb/Namespace.h

29 lines
885 B
C
Raw Normal View History

LibWeb: Add namespace to Element
2020-10-10 02:48:05 +01:00
/*
* Copyright (c) 2020, the SerenityOS developers.
*
Everything: Move to SPDX license identifiers in all files. SPDX License Identifiers are a more compact / standardized way of representing file license information. See: https://spdx.dev/resources/use/#identifiers This was done with the `ambr` search and replace tool. ambr --no-parent-ignore --key-from-file --rep-from-file key.txt rep.txt *
2021-04-22 01:24:48 -07:00
* SPDX-License-Identifier: BSD-2-Clause
LibWeb: Add namespace to Element
2020-10-10 02:48:05 +01:00
*/
#pragma once
AK+Everywhere: Rename FlyString to DeprecatedFlyString DeprecatedFlyString relies heavily on DeprecatedString's StringImpl, so let's rename it to A) match the name of DeprecatedString, B) write a new FlyString class that is tied to String.
2023-01-08 19:23:00 -05:00
#include <AK/DeprecatedFlyString.h>
LibWeb: Initialize static web strings during main-thread VM creation These are currently initialized in a [[gnu::constructor]], which has a weird initialization order. These constructors are invoked before main() and, incidentally, before any user-defined default constructors of the static strings they are initializing. This will become an issue when these strings are ported to FlyString, which has a user-defined default constructor. In that scenario, when the FlyString constructor is executed after the [[gnu::constructor]], the strings will be "reset" to the empty string. Instead of relying on a non-standard compiler extension here, let's just initialize these strings explicitly during main-thread VM creation, as this now happens in WebContent's main().
2023-03-18 10:39:37 -04:00
#include <AK/Error.h>
LibWeb: Add namespace to Element
2020-10-10 02:48:05 +01:00
namespace Web::Namespace {
#define ENUMERATE_NAMESPACES \
__ENUMERATE_NAMESPACE(HTML, "http://www.w3.org/1999/xhtml") \
__ENUMERATE_NAMESPACE(MathML, "http://www.w3.org/1998/Math/MathML") \
__ENUMERATE_NAMESPACE(SVG, "http://www.w3.org/2000/svg") \
__ENUMERATE_NAMESPACE(XLink, "http://www.w3.org/1999/xlink") \
__ENUMERATE_NAMESPACE(XML, "http://www.w3.org/XML/1998/namespace") \
__ENUMERATE_NAMESPACE(XMLNS, "http://www.w3.org/2000/xmlns/")
AK+Everywhere: Rename FlyString to DeprecatedFlyString DeprecatedFlyString relies heavily on DeprecatedString's StringImpl, so let's rename it to A) match the name of DeprecatedString, B) write a new FlyString class that is tied to String.
2023-01-08 19:23:00 -05:00
#define __ENUMERATE_NAMESPACE(name, namespace_) extern DeprecatedFlyString name;
LibWeb: Add namespace to Element
2020-10-10 02:48:05 +01:00
ENUMERATE_NAMESPACES
#undef __ENUMERATE_NAMESPACE
LibWeb: Initialize static web strings during main-thread VM creation These are currently initialized in a [[gnu::constructor]], which has a weird initialization order. These constructors are invoked before main() and, incidentally, before any user-defined default constructors of the static strings they are initializing. This will become an issue when these strings are ported to FlyString, which has a user-defined default constructor. In that scenario, when the FlyString constructor is executed after the [[gnu::constructor]], the strings will be "reset" to the empty string. Instead of relying on a non-standard compiler extension here, let's just initialize these strings explicitly during main-thread VM creation, as this now happens in WebContent's main().
2023-03-18 10:39:37 -04:00
ErrorOr<void> initialize_strings();
LibWeb: Add namespace to Element
2020-10-10 02:48:05 +01:00
}
Reference in a new issue Copy permalink