Popular posts

It may also be nice to know your use case and why wish so much to use the body?

In our case we need to do that. We have complete control over 3rd party code, and we rewrite stuff that misbehaves.

If that's the case, you are free and certainly able to fork Vue and remove the code that keeps it from mounting to body, or even better, submit a well-tested PR on github, along with a guide on how to deal with the problems of 3rd party-code competing for body.

We however have to focus our limited resources on supporting the needs of the larger community. As mounting to body can create problems that, as you explained, have to be worked around in 3rd-party code, we don't feel like it's a good idea to implement it as it will certainly introduce subtle bugs for many of our users that have to rely on 3rd party code they can't control.

As a sidenote, a little less agressive tone would help the conversation. And dan is awesome :)

Why we need access to body? First thing, it is programmatic access to setting and unsetting event handlers. It was extremely convenient to do it from the markup on a hash-routed website with a lot of views, especially if you want to map keyboard input for each route/view.

Another indispensable use case was to handle setting properties and hints for different screen readers. Some screen readers or accessibility tools effectively have their own mark-up formats, and dom addons, so effectively you have to develop a website for a certain browser set, AND, a specific screen reader.

Being able to programmatically set classes, lang, dir, and metadata properties (SEO meta, hints for ecommerce search engines) with router mounted on body was quite convenient too.

Finally, having document.body DOM object being rewritten from Vue's DOM also worked well with routable sites where a view/route has a code that does something to the body DOM object that is specific to that route AND/OR a reactive data in it. I'd say, this is the most hard thing to implement when the upstream code from Vue and 3rd party Vue modules has no awareness of such possibility.

Although i don't recommend overwriting the body, you can do something like this. https://jsfiddle.net/1u1h4e1k/1/

You could also get the innerHTML of the body to replace the body as is.