Stowage/ladybird
2
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-10-26 02:44:14 +00:00
Code Issues Projects Releases Packages Wiki Activity
ladybird/Libraries/LibWeb/DOM/Document.idl

171 lines
7.1 KiB
Text
Raw Normal View History

LibWeb: Add a default DocumentTimeline object to DOM::Document
2023-11-04 08:38:46 -07:00
#import <Animations/DocumentTimeline.idl>
LibWeb: Add stub implementation of FontFaceSet and Document.fonts This is now enough for duolingo to load and use its fallback fonts.
2024-05-07 14:49:31 -06:00
#import <CSS/FontFaceSet.idl>
LibWeb: Add imports to all IDL files that depend on others
2022-02-15 22:40:51 +03:30
#import <CSS/StyleSheetList.idl>
LibWeb: Implement `document.createCDATASection()`
2024-02-18 14:27:25 +00:00
#import <DOM/CDATASection.idl>
LibWeb: Add imports to all IDL files that depend on others
2022-02-15 22:40:51 +03:30
#import <DOM/Comment.idl>
#import <DOM/DOMImplementation.idl>
#import <DOM/DocumentFragment.idl>
LibWeb: Add styleSheets and adoptedStyleSheets attributes in ShadowRoot Co-authored-by: Simon Wanner <simon+git@skyrising.xyz>
2024-03-08 19:27:24 +01:00
#import <DOM/DocumentOrShadowRoot.idl>
LibWeb: Add imports to all IDL files that depend on others
2022-02-15 22:40:51 +03:30
#import <DOM/DocumentType.idl>
#import <DOM/Element.idl>
#import <DOM/Event.idl>
LibWeb: Replace ad-hoc EventHandler type with callback function typedef
2022-03-30 23:35:42 +03:00
#import <DOM/EventHandler.idl>
LibWeb: Add imports to all IDL files that depend on others
2022-02-15 22:40:51 +03:30
#import <DOM/HTMLCollection.idl>
#import <DOM/Node.idl>
LibWeb: Add basic support for DOM's NodeIterator and NodeFilter This patch adds NodeIterator (created via Document.createNodeIterator()) which allows you to iterate through all the nodes in a subtree while filtering with a provided NodeFilter callback along the way. This first cut implements the full API, but does not yet handle nodes being removed from the document while referenced by the iterator. That will be done in a subsequent patch.
2022-03-09 14:34:32 +01:00
#import <DOM/NodeFilter.idl>
#import <DOM/NodeIterator.idl>
LibWeb: Add imports to all IDL files that depend on others
2022-02-15 22:40:51 +03:30
#import <DOM/NodeList.idl>
LibWeb: Extract the ParentNode IDL mixin
2022-07-27 19:51:49 +01:00
#import <DOM/ParentNode.idl>
LibWeb: Add Document.createProcessingInstruction() These nodes don't really do anything interesting yet, but let's allow creating them. :^)
2022-12-13 13:24:56 +01:00
#import <DOM/ProcessingInstruction.idl>
LibWeb: Add imports to all IDL files that depend on others
2022-02-15 22:40:51 +03:30
#import <DOM/Range.idl>
#import <DOM/Text.idl>
LibWeb: Add support for DOM's TreeWalker This patch adds TreeWalker (created via Document.createTreeWalker()) which allows you to traverse a filtered view of the DOM in all directions.
2022-03-09 14:37:48 +01:00
#import <DOM/TreeWalker.idl>
LbiWeb: Return an HTMLAllCollection from document.all
2024-04-01 08:45:59 +02:00
#import <HTML/HTMLAllCollection.idl>
LibWeb: Add imports to all IDL files that depend on others
2022-02-15 22:40:51 +03:30
#import <HTML/HTMLElement.idl>
#import <HTML/HTMLHeadElement.idl>
#import <HTML/HTMLScriptElement.idl>
LibWeb: Convert the Location object to IDL This includes: - Moving it from Bindings/ to HTML/ - Renaming it from LocationObject to Location - Removing the manual definitions of the constructor and prototype - Removing special handling of the Location interface from the bindings generator - Converting the JS_DEFINE_NATIVE_FUNCTIONs to regular functions returning DeprecatedString instead of PrimitiveString - Adding missing (no-op) setters for the various attributes, which are expected to exist by the bindings generator
2023-01-18 17:41:12 +00:00
#import <HTML/Location.idl>
LibWeb: Add Document.getSelection
2022-12-09 18:59:13 +00:00
#import <Selection/Selection.idl>
LibWeb: Add imports to all IDL files that depend on others
2022-02-15 22:40:51 +03:30
LibWeb: Extract the ParentNode IDL mixin
2022-07-27 19:51:49 +01:00
// https://dom.spec.whatwg.org/#document
LibWeb: Implement Document named properties with light caching We now cache potentially named elements on the Document when elements are inserted and removed. This allows us to do lookup of what names are supported much faster than if we had to iterate the tree every time. This first cut doesn't implement the rules for 'exposed' object and embed elements.
2024-02-15 14:43:44 -07:00
// https://html.spec.whatwg.org/multipage/dom.html#the-document-object
[Exposed=Window, LegacyOverrideBuiltins]
LibWeb: Start generating JS wrappers from (simplified) WebIDL :^) This patch introduces a hackish but functional IDL parser and uses it to generate the JS bindings for Node and Document. We'll see how far this simple parser takes us. The important thing right now is generating code, not being a perfect IDL parser. :^)
2020-06-20 22:09:38 +02:00
interface Document : Node {
LibWeb: Add constructor to Document IDL interface
2021-02-17 22:52:21 +01:00
constructor();
LibWeb: Update focus-related spec text Corresponds to https://github.com/whatwg/html/commit/03ab71775bd10f8ef250f44261154a759ce7a41f I've also split the `Document::has_focus()` method for clarity. Actually implementing the "has focus steps" turns out to be quite involved so I've left it for now.
2025-04-11 16:29:06 +01:00
[ImplementedAs=has_focus_for_bindings] boolean hasFocus();
LibWeb: Add Document.hasFocus() stub This always returns true for now. A proper implementation needs to check if the document is in the focused widget within an active window.
2022-02-03 20:06:54 +01:00
LibWeb: Expose the location object via Document.location Both Window.location and Document.location use the same instance of the Location object. Some sites use it via Window, some via Document.
2021-09-12 14:59:49 +01:00
[PutForwards=href, LegacyUnforgeable] readonly attribute Location? location;
LibWeb: Implement document.domain getter The document.domain setter is currently stubbed as that is a doozy to implement, given how much restrictions there are in place to try and prevent use of it and potential multi-process implications. This was the only thing preventing us from being able to start displaying ads delivered via Google Syndication.
2022-09-14 15:50:47 +01:00
attribute USVString domain;
LibWeb: Expose the location object via Document.location Both Window.location and Document.location use the same instance of the Location object. Some sites use it via Window, some via Document.
2021-09-12 14:59:49 +01:00
LibWeb: Add initial implementation of document.implementation
2020-11-13 06:08:06 +00:00
readonly attribute DOMImplementation implementation;
LibWeb: Bring Document closer to spec
2022-04-12 13:19:35 -03:00
[ImplementedAs=url_string] readonly attribute USVString URL;
readonly attribute USVString documentURI;
LibWeb: Use standardized encoding names, add encoding attribute to document
2020-11-13 11:16:28 +00:00
readonly attribute DOMString characterSet;
readonly attribute DOMString charset;
readonly attribute DOMString inputEncoding;
LibWeb: Add contentType attribute to Document
2020-11-13 05:02:15 +00:00
readonly attribute DOMString contentType;
LibWeb: Return a WindowProxy from `document.defaultView` This aligns our implementation with the most recent specification steps.
2024-09-21 06:25:26 +01:00
readonly attribute WindowProxy? defaultView;
LibWeb: Expose the Window object as Document.defaultView This should really be a WindowProxy? but since we don't have anything representing that concept yet, let's just expose the Window object directly so document.defaultView.foo works. :^)
2021-02-21 21:24:11 +01:00
LibWeb: Add basic support for dynamic markup insertion This implements basic support for dynamic markup insertion, adding * Document::open() * Document::write(Vector<String> const&) * Document::writeln(Vector<String> const&) * Document::close() The HTMLParser is modified to make it possible to create a script-created parser which initially only contains a HTMLTokenizer without any data. Aditionally the HTMLParser::run method gains an overload which does not modify the Document and does not run HTMLParser::the_end() so that we can reenter the parser at a later time. Furthermore all FIXMEs that consern the insertion point are implemented wich is defined in the HTMLTokenizer. Additionally the following member-variables of the HTMLParser are now exposed by getter funcions: * m_tokenizer * m_aborted * m_script_nesting_level The HTMLTokenizer is modified so that it contains an insertion point which keeps track of where the next input from the Document::write functions will be inserted. The insertion point is implemented as the charakter offset into m_decoded_input and a boolean describing if the insertion point is defined. Functions to update, check and {re}store the insertion point are also added. The function HTMLTokenizer::insert_eof is added to tell a script-created parser that document::close was called and HTMLParser::the_end() should be called. Lastly an explicit default constructor is added to HTMLTokenizer to create a empty HTMLTokenizer into which data can be inserted.
2022-02-19 15:58:21 +01:00
[CEReactions] Document open(optional DOMString unused1, optional DOMString unused2);
LibWeb: Implement document.open(string, string, string)
2022-11-15 02:30:15 +02:00
WindowProxy? open(USVString url, DOMString name, DOMString features);
LibWeb: Add basic support for dynamic markup insertion This implements basic support for dynamic markup insertion, adding * Document::open() * Document::write(Vector<String> const&) * Document::writeln(Vector<String> const&) * Document::close() The HTMLParser is modified to make it possible to create a script-created parser which initially only contains a HTMLTokenizer without any data. Aditionally the HTMLParser::run method gains an overload which does not modify the Document and does not run HTMLParser::the_end() so that we can reenter the parser at a later time. Furthermore all FIXMEs that consern the insertion point are implemented wich is defined in the HTMLTokenizer. Additionally the following member-variables of the HTMLParser are now exposed by getter funcions: * m_tokenizer * m_aborted * m_script_nesting_level The HTMLTokenizer is modified so that it contains an insertion point which keeps track of where the next input from the Document::write functions will be inserted. The insertion point is implemented as the charakter offset into m_decoded_input and a boolean describing if the insertion point is defined. Functions to update, check and {re}store the insertion point are also added. The function HTMLTokenizer::insert_eof is added to tell a script-created parser that document::close was called and HTMLParser::the_end() should be called. Lastly an explicit default constructor is added to HTMLTokenizer to create a empty HTMLTokenizer into which data can be inserted.
2022-02-19 15:58:21 +01:00
[CEReactions] undefined close();
LibWeb: Update Document.write spec steps The spec changes seem to mostly be about introducing a TrustedHTML type which we do not yet support, so we have a couple of FIXMEs. TrustedTypes::InjectionSink is an attempt at matching the spec, but it's not entirely clear to me how it should work. I'm sure it'll get revisited once we start implementing trusted types.
2025-02-24 12:53:37 +00:00
// FIXME: [CEReactions] undefined write((TrustedHTML or DOMString)... text);
LibWeb: Add basic support for dynamic markup insertion This implements basic support for dynamic markup insertion, adding * Document::open() * Document::write(Vector<String> const&) * Document::writeln(Vector<String> const&) * Document::close() The HTMLParser is modified to make it possible to create a script-created parser which initially only contains a HTMLTokenizer without any data. Aditionally the HTMLParser::run method gains an overload which does not modify the Document and does not run HTMLParser::the_end() so that we can reenter the parser at a later time. Furthermore all FIXMEs that consern the insertion point are implemented wich is defined in the HTMLTokenizer. Additionally the following member-variables of the HTMLParser are now exposed by getter funcions: * m_tokenizer * m_aborted * m_script_nesting_level The HTMLTokenizer is modified so that it contains an insertion point which keeps track of where the next input from the Document::write functions will be inserted. The insertion point is implemented as the charakter offset into m_decoded_input and a boolean describing if the insertion point is defined. Functions to update, check and {re}store the insertion point are also added. The function HTMLTokenizer::insert_eof is added to tell a script-created parser that document::close was called and HTMLParser::the_end() should be called. Lastly an explicit default constructor is added to HTMLTokenizer to create a empty HTMLTokenizer into which data can be inserted.
2022-02-19 15:58:21 +01:00
[CEReactions] undefined write(DOMString... text);
LibWeb: Update Document.write spec steps The spec changes seem to mostly be about introducing a TrustedHTML type which we do not yet support, so we have a couple of FIXMEs. TrustedTypes::InjectionSink is an attempt at matching the spec, but it's not entirely clear to me how it should work. I'm sure it'll get revisited once we start implementing trusted types.
2025-02-24 12:53:37 +00:00
// FIXME: [CEReactions] undefined writeln((TrustedHTML or DOMString)... text);
LibWeb: Add basic support for dynamic markup insertion This implements basic support for dynamic markup insertion, adding * Document::open() * Document::write(Vector<String> const&) * Document::writeln(Vector<String> const&) * Document::close() The HTMLParser is modified to make it possible to create a script-created parser which initially only contains a HTMLTokenizer without any data. Aditionally the HTMLParser::run method gains an overload which does not modify the Document and does not run HTMLParser::the_end() so that we can reenter the parser at a later time. Furthermore all FIXMEs that consern the insertion point are implemented wich is defined in the HTMLTokenizer. Additionally the following member-variables of the HTMLParser are now exposed by getter funcions: * m_tokenizer * m_aborted * m_script_nesting_level The HTMLTokenizer is modified so that it contains an insertion point which keeps track of where the next input from the Document::write functions will be inserted. The insertion point is implemented as the charakter offset into m_decoded_input and a boolean describing if the insertion point is defined. Functions to update, check and {re}store the insertion point are also added. The function HTMLTokenizer::insert_eof is added to tell a script-created parser that document::close was called and HTMLParser::the_end() should be called. Lastly an explicit default constructor is added to HTMLTokenizer to create a empty HTMLTokenizer into which data can be inserted.
2022-02-19 15:58:21 +01:00
[CEReactions] undefined writeln(DOMString... text);
LibWeb: Add stubs for document.write and document.writeln ACID3 test page throws exception about document.write. Let's at least get rid of it by defining these stubs. I added document.writeln too because it is similar.
2022-02-15 17:36:27 +01:00
LibWeb: Implement unsafe HTML parsing methods Both Element's and ShadowRoot's setHTMLUnsafe, and Document's static parseHTMLUnsafe methods are implemented.
2024-06-25 20:55:58 +01:00
// FIXME: static Document parseHTMLUnsafe((TrustedHTML or DOMString) html);
static Document parseHTMLUnsafe(DOMString html);
LibWeb: Stub out Document.cookie We don't get/set anything, but at least scripts that access document cookies can now progress further. :^)
2021-03-14 16:35:28 +01:00
attribute DOMString cookie;
Meta: Disallow links to single-page HTML spec
2025-02-04 13:01:46 +01:00
// https://html.spec.whatwg.org/multipage/obsolete.html#Document-partial
LibWeb/DOM: Implement the Document object's partial attributes
2024-04-18 13:58:48 -06:00
[CEReactions, LegacyNullToEmptyString] attribute DOMString fgColor;
[CEReactions, LegacyNullToEmptyString] attribute DOMString linkColor;
[CEReactions, LegacyNullToEmptyString] attribute DOMString vlinkColor;
[CEReactions, LegacyNullToEmptyString] attribute DOMString alinkColor;
[CEReactions, LegacyNullToEmptyString] attribute DOMString bgColor;
LibWeb: Add naive support for the Document.referrer attribute It always returns the empty string for now.
2021-09-11 12:29:06 +02:00
readonly attribute USVString referrer;
LibWeb: Implement the Document.activeElement attribute We were already tracking the active element in DOM::Document, so all we had to do here was add the attribute to Document.idl :^)
2021-09-27 16:51:10 +02:00
readonly attribute Element? activeElement;
LibWeb: Start generating JS wrappers from (simplified) WebIDL :^) This patch introduces a hackish but functional IDL parser and uses it to generate the JS bindings for Node and Document. We'll see how far this simple parser takes us. The important thing right now is generating code, not being a perfect IDL parser. :^)
2020-06-20 22:09:38 +02:00
Element? getElementById(DOMString id);
LibWeb: Return a NodeList from `document.getElementsByName()` This aligns our implementation with the specification.
2024-07-22 21:44:05 +01:00
NodeList getElementsByName([FlyString] DOMString name);
LibWeb: Pass a FlyString to getElementsByTagNameNS
2024-05-12 14:50:45 +12:00
HTMLCollection getElementsByTagName([FlyString] DOMString tagName);
HTMLCollection getElementsByTagNameNS([FlyString] DOMString? namespace, [FlyString] DOMString localName);
LibWeb: Implement a slow but functional HTMLCollection :^) HTMLCollection is an awkward legacy interface from the DOM spec. It provides a live view of a DOM subtree, with some kind of filtering that determines which elements are part of the collection. We now return HTMLCollection objects from these APIs: - getElementsByClassName() - getElementsByName() - getElementsByTagName() This initial implementation does not do any kind of caching, since that is quite a tricky problem, and there will be plenty of time for tricky problems later on when the engine is more mature.
2021-04-22 21:11:20 +02:00
HTMLCollection getElementsByClassName(DOMString className);
LibWeb: Expose ParentNode.{first,last}ElementChild I needed these to write the event dispatcher test.
2020-11-21 18:49:09 +00:00
LibWeb: Add missing [SameObject] extended attributes in IDL files
2022-11-24 19:15:33 +01:00
[SameObject] readonly attribute HTMLCollection applets;
[SameObject] readonly attribute HTMLCollection anchors;
[SameObject] readonly attribute HTMLCollection images;
[SameObject] readonly attribute HTMLCollection embeds;
[SameObject] readonly attribute HTMLCollection plugins;
[SameObject] readonly attribute HTMLCollection links;
[SameObject] readonly attribute HTMLCollection forms;
[SameObject] readonly attribute HTMLCollection scripts;
LibWeb: Implement document.applets This is a legacy interface that returns an always-empty HTMLCollection.
2021-04-22 22:11:42 +02:00
LbiWeb: Return an HTMLAllCollection from document.all
2024-04-01 08:45:59 +02:00
readonly attribute HTMLAllCollection all;
LibWeb: Implement basic support for Document.all The finer details are missing here, but the basic API is up.
2022-09-18 02:17:11 +02:00
LibWeb: Add methods to Document that must do nothing This change adds the `clear()`, `captureEvents()` and `releaseEvents()` methods to the document object. These methods are obsolete, but are still included in the HTML specification, which says they must do nothing.
2024-04-14 07:25:49 +01:00
undefined clear();
undefined captureEvents();
undefined releaseEvents();
LibWeb: Add a bunch of missing CEReactions This is almost guaranteed not to be all CEReactions we need to add, but this puts us in a much better situation.
2023-03-01 01:45:18 +00:00
[CEReactions, NewObject] Element createElement(DOMString tagName, optional (DOMString or ElementCreationOptions) options = {});
LibWeb: Use Optional<FlyString> directly in Document & DOMImplementation Use the [FlyString] extended attribute to allow these functions to take an Optional<FlyString> directly, allowing us to tidy up some conversions from Optional<String>.
2024-01-12 22:01:45 +13:00
[CEReactions, NewObject] Element createElementNS([FlyString] DOMString? namespace, DOMString qualifiedName, optional (DOMString or ElementCreationOptions) options = {});
LibWeb: Add Comment and DocumentFragment bindings, move querySelector... ...{All} to ParentNode. Exposes createDocumentFragment and createComment on Document. Stubs out the document.body setter. Also adds ParentNode back :^).
2020-08-17 19:14:30 +01:00
DocumentFragment createDocumentFragment();
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 12:05:52 -04:00
Text createTextNode(Utf16DOMString data);
[NewObject] CDATASection createCDATASection(Utf16DOMString data);
Comment createComment(Utf16DOMString data);
[NewObject] ProcessingInstruction createProcessingInstruction(DOMString target, Utf16DOMString data);
LibWeb: Add Document.createProcessingInstruction() These nodes don't really do anything interesting yet, but let's allow creating them. :^)
2022-12-13 13:24:56 +01:00
LibWeb: Implement Document.createAttribute{,NS}()
2023-03-10 14:56:03 +01:00
[NewObject] Attr createAttribute(DOMString localName);
LibWeb: Use Optional<FlyString> directly in Document & DOMImplementation Use the [FlyString] extended attribute to allow these functions to take an Optional<FlyString> directly, allowing us to tidy up some conversions from Optional<String>.
2024-01-12 22:01:45 +13:00
[NewObject] Attr createAttributeNS([FlyString] DOMString? namespace, DOMString qualifiedName);
LibWeb: Implement Document.createAttribute{,NS}()
2023-03-10 14:56:03 +01:00
LibWeb: Add Document.createRange() Also tidy up DOM::Range a little bit while we're here, and unify the way we create them to use a delegating constructors.
2021-02-21 23:41:54 +01:00
Range createRange();
LibWeb: Add a basic implementation of Document.createEvent() This is a legacy function providing a way of constructing events without using their constructors exposed on the global object. We don't have many of the events it supports yet, nor can we throw a DOMException from it, so that's two FIXMEs for later.
2021-04-10 18:58:00 +02:00
Event createEvent(DOMString interface);
LibWeb: Start generating JS wrappers from (simplified) WebIDL :^) This patch introduces a hackish but functional IDL parser and uses it to generate the JS bindings for Node and Document. We'll see how far this simple parser takes us. The important thing right now is generating code, not being a perfect IDL parser. :^)
2020-06-20 22:09:38 +02:00
LibWeb: Implement Document.importNode
2021-09-26 17:41:51 +01:00
[CEReactions, NewObject] Node importNode(Node node, optional boolean deep = false);
LibWeb: Make the node mutation algorithms more spec compliant The mutation algorithms now more closely follow the spec and fixes some assertion failures in tests such as Acid3 and Dromaeo. The main thing that is missing right now is passing exceptions to the bindings layer. This is because of issue #6075. I spent a while trying to work it out and got so frustrated I just left it as a FIXME. Besides that, the algorithms bail at the appropriate points. This also makes the adopting steps in the document more spec compliant as it's needed by the insertion algorithm. While I was at it, I added the adoptNode IDL binding. This adds a bunch of ancestor/descendant checks to TreeNode as well. I moved the "remove_all_children" function to Node as it needs to use the full remove algorithm instead of simply removing it from the child list.
2021-04-06 19:34:49 +01:00
[CEReactions, ImplementedAs=adopt_node_binding] Node adoptNode(Node node);
LibWeb: Implement quirks mode detection This allows us to determine which mode to render the page in. Exposes "doctype" and "compatMode" on Document. Exposes "name", "publicId" and "systemId" on DocumentType.
2020-07-18 21:17:17 +01:00
readonly attribute DOMString compatMode;
readonly attribute DocumentType? doctype;
LibWeb: Add the Document.documentElement API Also change DOM::Document::document_element() to return an Element* and not an HTML::HTMLHtmlElement since that's not the only kind of documentElement we might encounter.
2020-08-03 13:30:18 +02:00
readonly attribute Element? documentElement;
LibWeb: Implement Document.dir This was seen getting called on stuff.co.nz (before it crashes due to an unrelated navigation bug)
2024-05-13 23:47:50 +12:00
[CEReactions] attribute DOMString dir;
LibWeb: Add a bunch of missing CEReactions This is almost guaranteed not to be all CEReactions we need to add, but this puts us in a much better situation.
2023-03-01 01:45:18 +00:00
[CEReactions] attribute HTMLElement? body;
LibWeb: Add Comment and DocumentFragment bindings, move querySelector... ...{All} to ParentNode. Exposes createDocumentFragment and createComment on Document. Stubs out the document.body setter. Also adds ParentNode back :^).
2020-08-17 19:14:30 +01:00
readonly attribute HTMLHeadElement? head;
LibWeb: Flesh out prepare_script and execute_script This fills in a bunch of the FIXMEs that was in prepare_script. execute_script is almost finished, it's just missing the module side. As an aside, let's not assert when inserting a script element with innerHTML.
2021-01-28 20:31:20 +00:00
readonly attribute HTMLScriptElement? currentScript;
LibWeb: Expose Document.body to the web Also, make it return a HTMLElement since Document.body should actually return the frameset element in a frame-based document.
2020-06-21 00:59:28 +02:00
LibWeb: Add support for document.lastModified
2024-04-01 22:18:00 +02:00
readonly attribute DOMString lastModified;
LibWeb: Implement document ready state
2020-08-31 13:56:16 +01:00
readonly attribute DOMString readyState;
LibWeb: Add a bunch of missing CEReactions This is almost guaranteed not to be all CEReactions we need to add, but this puts us in a much better situation.
2023-03-01 01:45:18 +00:00
[CEReactions] attribute DOMString title;
LibWeb: Make document.title accessible from JavaScript :^)
2020-12-06 21:39:36 +01:00
IDL: Fix syntax errors All attributes must have an "attribute" keyword, and "any?" is invalid (as "any" includes "null" as well).
2023-11-07 19:30:05 -07:00
readonly attribute boolean hidden;
readonly attribute DOMString visibilityState;
LibWeb: Support Document.hidden and Document.visibilityState These just act as if the document is always visible for now.
2021-09-27 16:02:13 +02:00
LibWeb: Add basic support for DOM's NodeIterator and NodeFilter This patch adds NodeIterator (created via Document.createNodeIterator()) which allows you to iterate through all the nodes in a subtree while filtering with a provided NodeFilter callback along the way. This first cut implements the full API, but does not yet handle nodes being removed from the document while referenced by the iterator. That will be done in a subsequent patch.
2022-03-09 14:34:32 +01:00
[NewObject] NodeIterator createNodeIterator(Node root, optional unsigned long whatToShow = 0xFFFFFFFF, optional NodeFilter? filter = null);
LibWeb: Add support for DOM's TreeWalker This patch adds TreeWalker (created via Document.createTreeWalker()) which allows you to traverse a filtered view of the DOM in all directions.
2022-03-09 14:37:48 +01:00
[NewObject] TreeWalker createTreeWalker(Node root, optional unsigned long whatToShow = 0xFFFFFFFF, optional NodeFilter? filter = null);
LibWeb: Add Document.getSelection
2022-12-09 18:59:13 +00:00
Selection? getSelection();
LibWeb: Add a default DocumentTimeline object to DOM::Document
2023-11-04 08:38:46 -07:00
LibWeb: Implement `document.designMode` Setting this attribute to "on" makes the entire document editable.
2024-02-10 15:23:19 +00:00
[CEReactions] attribute DOMString designMode;
LibWeb: Add a default DocumentTimeline object to DOM::Document
2023-11-04 08:38:46 -07:00
// https://www.w3.org/TR/web-animations-1/#extensions-to-the-document-interface
readonly attribute DocumentTimeline timeline;
LibWeb: Implement `document.elementFromPoint()` This function uses our existing hit testing code to determine the topmost element at the given coordinates relative to the viewport.
2024-02-06 06:02:51 +00:00
// https://drafts.csswg.org/cssom-view/#extensions-to-the-document-interface
Element? elementFromPoint(double x, double y);
LibWeb: Implement document.elementsFromPoint This API seems to be used by WPT for sending synthetic input events. Implementing the naive translation of elementFromPoint to the spec steps for this algorithm turns 4 'tests had errors unexpectedly' and 3 'tests had timeouts unexpectedly' into 1 pass and 7 'tests had unexpected subtest results' on the infrastructure/ subdirectory of WPT.
2024-02-09 13:50:44 -07:00
sequence<Element> elementsFromPoint(double x, double y);
LibWeb: Implement `document.scrollingElement` This returns a reference to the element that scrolls the document. In standards mode it is equivalent to `document.documentElement`.
2024-02-15 23:14:55 +00:00
readonly attribute Element? scrollingElement;
LibWeb: Stub out all the functions from the execCommand spec Per the specification, it's ok if we say that nothing is supported. It's not ok if we say something is supported but do nothing, apparently.
2024-02-15 16:47:29 -07:00
// https://w3c.github.io/editing/docs/execCommand/
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
// FIXME: [CEReactions] boolean execCommand(DOMString commandId, optional boolean showUI = false, optional (TrustedHTML or DOMString) value = "");
LibWeb: Port document.execCommand and InputEvent to UTF-16
2025-07-25 15:57:20 -04:00
[CEReactions] boolean execCommand(DOMString commandId, optional boolean showUI = false, optional Utf16DOMString value = "");
LibWeb: Stub out all the functions from the execCommand spec Per the specification, it's ok if we say that nothing is supported. It's not ok if we say something is supported but do nothing, apparently.
2024-02-15 16:47:29 -07:00
boolean queryCommandEnabled(DOMString commandId);
boolean queryCommandIndeterm(DOMString commandId);
boolean queryCommandState(DOMString commandId);
boolean queryCommandSupported(DOMString commandId);
DOMString queryCommandValue(DOMString commandId);
LibWeb: Support Document.onreadystatechange This is just a standard IDL event attribute handler. Fixes at least one WPT test: https://wpt.live/html/dom/documents/resource-metadata-management/document-readyState.html
2024-10-08 16:24:23 +02:00
// special event handler IDL attributes that only apply to Document objects
[LegacyLenientThis] attribute EventHandler onreadystatechange;
LibWeb: Support Document.onvisibilitychange We don't have a way to trigger this from a test, but the fix is so simple that we might as well get it in. :^)
2024-10-08 16:27:40 +02:00
attribute EventHandler onvisibilitychange;
LibWeb: Implement Document.rootElement (SVG2 extension to Document)
2025-05-09 00:30:40 +02:00
// https://www.w3.org/TR/SVG2/struct.html#InterfaceDocumentExtensions
readonly attribute SVGSVGElement? rootElement;
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 21:26:42 +00:00
};
LibWeb: Add the GlobalEventHandlers IDL mixin
2022-04-01 22:00:22 +03:00
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
dictionary ElementCreationOptions {
DOMString is;
};
LibWeb: Resolve circular IDL imports These circular imports led to the generator silently failing to generate the required methods/properties.
2022-07-30 11:31:17 +01:00
Document includes ParentNode;
LibWeb: Correct typo in Document.idl Makes me wonder how things were working when Document was never including GlobalEventHandlers.
2022-07-27 19:51:06 +01:00
Document includes GlobalEventHandlers;
LibWeb: Add styleSheets and adoptedStyleSheets attributes in ShadowRoot Co-authored-by: Simon Wanner <simon+git@skyrising.xyz>
2024-03-08 19:27:24 +01:00
Document includes DocumentOrShadowRoot;
LibWeb: Add stub implementation of FontFaceSet and Document.fonts This is now enough for duolingo to load and use its fallback fonts.
2024-05-07 14:49:31 -06:00
Document includes FontFaceSource;
Reference in a new issue Copy permalink