Popescu Dan

By nested I was thinking more about something like this: ```html ... ... ```

It was just a quick example to show a possible situation where the teleport targets have a non-trivial structure.

bodyHtmlStart/End sounds good to me

At least for teleports the body start and end strings should be functions with access to ssrContext.

I meant the ctx passed to renderTo... functions (in the PR it's called ssrContext)

A sample tamplate would look like this when using vike without vike-vue: ```js const documentHtml = escapeInject` ${ faviconTag } ${ titleTag } ${ descriptionTag } ${ headHtml } ${...

> I ain’t that familiar with Vue but sounds good to me. @pdanpdan WDYT? From my point of view the most flexible (and simple to use) would be the method...

I still have the same concerns as before: - now the default HTML has an extra element most people don't need, and that does not fit the needs of most...

QFab and QFabAction should be fixed by 31f3d7d52226e93b211d47c6cfce2a2b781bad1d

QButton and QCheckbox (and some other) should be fixed in a95591ec6f1fad6ee795f5f8c8298a5ed056a248