Joshua Thijssen

We currently have a style calculator which can calculate the CSS properties per document node. This is the first step of the rendering pipeline which outputs the render tree

Don't worry about the authors file. The check isn't that good, and should be either be changed or even removed (and maybe there are other - better - actions available...

This is pretty much implemented in the new style CSS system

👍

This is the html5lib-test repo which can be found [here](https://github.com/html5lib/html5lib-tests). Maybe a message should be displayed on where to find the repo when it isn't detected or given as argument.

Does this mean we have to keep an updated version of html5lib tests in our repo, or can we use something like git submodules for this purpose? I don't have...

ok.. let's try and see how the vendoring would work. I'm not 100% happy with having 3rd party code inside the repo, but I think it will be the best...

Let's wait for now. It seems a relative easy process to move this, but since the parser is still a big work in progress (making sure all tests pass takes...

Do we have some research on how other engines expose their API? We don't need to mimic them 1 on 1, but it gives us at least an idea on...

Are we copying / transforming these tests into our codebase? Or could we use the tests "as-is" and have our code transform anything? I would opt for the latter, as...