Eike

It also breaks setext/underline style headers: ``` Headline -------- ``` becomes ``` Headline-------- ```

Here is a WIP patch for adapting the Qt wrapper for litehtml 0.8 https://codereview.qt-project.org/c/playground/qlitehtml/+/479103. Unfortunately `element::get_position()` and `document->root()->get_element_by_point(...)` were removed, and I don't see a way to get the render_item...

It looks like the render_item has a backpointer to the `src_el()`, it would be great if we had it the other way round, element->render_item, too

I think the main difference is that "position" seems to be the position in the parent, and "placement" is relative to the document. I've updated https://codereview.qt-project.org/c/playground/qlitehtml/+/479103 with workarounds for the...

So, I've finished the patch updating the Qt backend to litehtml v0.9 . Not sure if it works correctly in all cases (z-ordering and fixed position elements are ignored for...

> not correctly computing the overall document size Right, and the top navigation bar of the Qt documentation is too wide as well. It wasn't fixed for me just by...

Maybe someone with more C++ foo has an idea why that happens in the first place even when not using `using namespace std;`