DOM class implementation. #8

New Issue

azpect · 2025-10-14T12:52:57-07:00

azpect commented

2025-10-14 12:52:57 -07:00

There should exist a DOM (document object model) class that is the result of the parser's execution.

This class should be a part of the parser class. i.e. a parser has a DOM.

Once the parser is completed, the DOM should reside (completed) inside, where the DOM parser can execute and generate an output string.

There should exist a DOM (document object model) class that is the result of the parser's execution. This class should be a part of the `parser` class. i.e. a parser **has** a DOM. Once the parser is completed, the DOM should reside (completed) inside, where the DOM parser can execute and generate an output string.

azpect added the

Kind/Feature

Priority

Medium

labels 2025-10-14 12:52:57 -07:00

azpect added this to the (SPRINT) Internal HTML Tree Generation (DOM) project 2025-10-14 12:52:57 -07:00

azpect moved this to To Do in (SPRINT) Internal HTML Tree Generation (DOM) on 2025-10-14 12:53:02 -07:00

azpect closed this issue

2025-10-17 11:56:13 -07:00

azpect moved this to Done in (SPRINT) Internal HTML Tree Generation (DOM) on 2025-10-17 13:19:38 -07:00

Sign in to join this conversation.