w3c/DOM-Parsing Issues

Last updated Nov 23, 2024, 5:50:57 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

Untriaged

Try to triage issues within . [ More Info ]

Issue Title Within SLO On maintainers' plates for Time left Time past SLO
#25 Please make it clear that the require well-formed flag is optional (you might also want to make flag is part of the term as we do elsewhere) ❌
#26 Flags do not have true and false as values ❌
#37 Tests ❌
#43 Editorial error in 'XML serializing an Element node' ❌
#44 It's possible for 'generate a prefix' algorithm to generate a prefix conflicting with an existing one ❌
#45 It's possible that 'retrieve a preferred prefix string' returns a wrong prefix for the specified namespace ❌
#49 Do not forbid resetting the default namespace… ❌
#50 Serialization of the XML declaration ❌
#52 XMLSerializer: Should prefer the default namespace to a prefix declared in an ancestor ❌
#63 insertAdjacentHTML should return a NodeList ❌
#71 DocumentType XML serialization doesn't handle the presence of double quotes in system ID ❌
#72 "XML serialization of the attributes" appears to be missing "If" at the start of step 3.5.2.4 ❌
#74 Broken references in DOM Parsing and Serialization ❌
#75 Prefix collision issues in serialization algorithms ❌
#76 Proposal on how to deal with <script>-blocks when appending to the DOM ❌
#83 No-namespace element serialized in a namespace if DOM Level 1 xmlns attribute set ❌
#84 Provide an API to serialize with the "require well-formed" parameter set to true ❌
#85 Serializing outerHTML of an HTML node that got adopted by an XML document ❌