ladybird/Libraries/LibWeb/DOM/DOMImplementation.idl

#import <DOM/Document.idl>
#import <DOM/XMLDocument.idl>

// https://dom.spec.whatwg.org/#domimplementation
[Exposed=Window]
interface DOMImplementation {
    [NewObject] DocumentType createDocumentType(DOMString qualifiedName, DOMString publicId, DOMString systemId);
    [NewObject] XMLDocument createDocument([FlyString] DOMString? namespace, [LegacyNullToEmptyString] DOMString qualifiedName, optional DocumentType? doctype = null);
    [NewObject] Document createHTMLDocument(optional Utf16DOMString title);

    boolean hasFeature(); // useless; always returns true
};
LibWeb: Add imports to all IDL files that depend on others 2022-02-15 16:10:51 -03:00			`#import <DOM/Document.idl>`
LibWeb: Make DOMImplementation IDL return an XMLDocument Which the implementation was already doing, so no behaviour change :^) 2024-05-19 06:38:56 -03:00			`#import <DOM/XMLDocument.idl>`
LibWeb: Add imports to all IDL files that depend on others 2022-02-15 16:10:51 -03:00
LibWeb: Add Exposed attribute and IDL spec links where missing The intent is to use these to autogenerate prototype declarations for Window and WorkerGlobalScope classes. And the spec links are just nice to have :^) 2022-10-07 19:45:09 -03:00			`// https://dom.spec.whatwg.org/#domimplementation`
LibWeb: Switch IDL from UseNewAKString to UseDeprecatedAKString NewAKString is effectively the default for any new IDL interface, so let's mark this as the default behavior. It also makes it much easier to figure out whatever interfaces are still left to port over to new AK String. 2023-09-02 11:00:01 -03:00			`[Exposed=Window]`
LibWeb: Add initial implementation of document.implementation 2020-11-13 03:08:06 -03:00			`interface DOMImplementation {`
LibWeb: Update DOM IDL specs I noticed some of these were running behind the upstream spec. 2024-10-14 06:55:51 -03:00			`[NewObject] DocumentType createDocumentType(DOMString qualifiedName, DOMString publicId, DOMString systemId);`
LibWeb: Make DOMImplementation IDL return an XMLDocument Which the implementation was already doing, so no behaviour change :^) 2024-05-19 06:38:56 -03:00			`[NewObject] XMLDocument createDocument([FlyString] DOMString? namespace, [LegacyNullToEmptyString] DOMString qualifiedName, optional DocumentType? doctype = null);`
LibWeb+LibUnicode+WebContent: Port DOM:CharacterData to UTF-16 This replaces the underlying storage of CharacterData with Utf16String and deals with the fallout. 2025-07-24 13:05:52 -03:00			`[NewObject] Document createHTMLDocument(optional Utf16DOMString title);`
LibWeb: Add initial implementation of document.implementation 2020-11-13 03:08:06 -03:00
LibWeb: Update DOM IDL specs I noticed some of these were running behind the upstream spec. 2024-10-14 06:55:51 -03:00			`boolean hasFeature(); // useless; always returns true`
LibWeb: Expect IDL namespace to end with semicolon From the Web IDL spec: https://heycam.github.io/webidl/#prod-Namespace Namespace :: namespace identifier { NamespaceMembers } ; 2020-12-09 18:26:42 -03:00			`};`