Ivan Demidov

> I would prefer to something like this in posthtml-mso instead of here cause there might be other plugins which needs custom HTML structure and posthtml 's renderer can be...

For now, move it to `posthtml-mso`

@anikethsaha > can we support officially a way to override the renderer like it is done for parser ? I don't see any reason why we shouldn't do this, and...

The decisions made in `posthtml-beautify` were caused by the fact that the parser didn’t process correctly `Downlevel-revealed`, I have a solution that processes correctly `Downlevel-revealed` and many other problems in...

Thoughts for implementation 1. First of all, it is necessary to designate the opening and closing tag **`from`** ```html ``` **`to`** ```html ``` thereby we get a tree ```js [...

> I would definitely not want to force the user into defining opening/closing tags through `type` attributes. This is an implementation detail that they shouldn’t have to care about. The...

@cossssmin All attempts were in vain, the absence of a closing tag takes the tree deeper, its presence makes all the content content.

@cossssmin Hi, what was the reason to close this issue?

> Based on your previous comment - if we can still tackle this, my bad 😬 We can, I will try to allocate time for this.

@cossssmin Hi, I think it's worth trying the new option using for `posthtml` new version of render with option [closeas](https://github.com/posthtml/posthtml-render#closeas)