render entities as-is (prevent server-client dom mismatch), fixes #6345

[buhrmi]

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact and migration path for existing applications:

The PR fulfills these requirements:

• It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
• New/updated tests are included

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

[HerringtonDarkholme]

I guess the decode is done by intention. Note compiler is shared across ssr, client side template and vue-loader, I wonder if decode is necessary under different situation. However, I'm not familiar enough to give confident answer.

Would you mind digging deeper for this? Thanks!

[yyx990803]

Thanks for the PR, but the decode in the parser is necessary for correct client-side behavior. The bug was actually introduced by the SSR optimizing compiler in 2.4 and a proper fix is provided in 172dbf9