tomtheisen

I found a work-around to this. If you navigate to the element you want to screenshot in the devtools document inspector, you can screenshot the node from there successfully.

It was intentional at the time, but in retrospect it may have been a mistake. I might consider the effect it would have on backward compatibility. I'm not sure how...

> ```ts > const table = document.createElement('table'); > table.innerHTML = ''; > console.log(table.innerHTML); > ``` I don't think this is showing what you think it is showing. This is a...

At a minimum the warning shouldn't claim that this is due to a spec. It seems this is constraint introduced by the implementation details of hydration. It could say something...

> Technically, that same spec says this too: > > > For historical reasons, certain elements have extra restrictions beyond even the restrictions given by their content model. > >...

> > In this scenario, I’m not sure how the ^text solution would apply or help, since the text is part of the CMS data structure. Could you provide further...

> Sure. I've done it this way. However, it's just a workaround and not a solution. I don't think it's a workaround because I don't think there's a bug here....

This is a difference between vue templates and HTML. `` is not special. `` works in a vue template. There's no way to achieve that at all in HTML without...