DOM tree creation

[jaytaph]

At this moment, the parser will output a node tree that is based on html5_paser/node structure. However, we ultimately need a DOM tree that allows user-agents to parse them. Also, during parsing, we might need the current DOM tree as well, as javascripts can be executed DURING the html5 parsing and change the dom.

The current node structure and DOM structure are both trees, and we might be able to generate a DOM tree straight away in the parser. But there are all kind of interfaces that we need to implement (this way, javascript can process the dom tree). This is still uncharted territory for me so any help and research is appreciated!

[Kiyoshika]

I've been playing around with the document output from the parser to understand how it works since i'm kinda interested in working with this (and also trying to learn Rust at the same time)

Was that the purpose of the HtmlElement struct in html5_parser/dom? To represent the DOM tree or did this have a different use case

[jaytaph]

There is no purpose for this at the moment. It is an initial setup that may or may not be used.

The dom specification can be found on https://dom.spec.whatwg.org/, but i haven't had time enough to read it thourougly and see how we can incorporate this in the current system.

[Kiyoshika]

I see, with the weekend coming up I will try reading through this and maybe start with at least a minimal foundation that can be expanded overtime. Or at the very least abstract the Document a bit it make it easier to work with the nodes for the user agents to interact with the items in the tree

[Kiyoshika]

Was reading through the spec this morning at work, I think I will try to cover some of the missing/incomplete interfaces (node, attributes, document) which will help with building out the whole DOM tree. Will probably create some PRs with small chunks at a time so I don't overload with a 10,000 line commit