Extend Blazor "insignificant whitespace trimming" into Razor Pages and MVC.

[Bartmax]

Based on Blazor whitespace trimming issue I create this one to track a feature request to extend that functionality to Razor Pages and MVC View (aka .cshtml filetypes)

I know that the motivation behind this improvement on blazor is about diffing the tree (something it doesn't happen on razor/mvc), but it also have other bonuses in regards to performance because the smaller payload and the fact that it looks like actually may be something very low cost since the work will be done by the blazor team, looks like a great fit to add value to the framework as a whole.

Here's one of many example/approaches on how one would implement a solution like that right now to minifying .cshtml files: https://debugandrelease.blogspot.com/2018/11/automatically-minifying-cshtml-files-in.html

as you can see, this requires lots of steps/works and extra dependencies,
joining forces with blazor team I think this could be a very consistent framework-wide feature.

[DamianEdwards]

I had made a comment in the PR to this effect and you beat me to logging an issue! 😄

[mkArtakMSFT]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[JesperTreetop]

Please consider this for the .NET 7 roadmap: #39504 . I have wanted whitespace trimming since about five seconds after using Razor for the first time in ASP.NET MVC 3 and it's one of the few blemishes in Razor's design.

Any after-the-fact approach has to either do buffering on the output or meddle with the generated .g.cs (and/or insert itself into the compiler pipeline), which is painful, dangerous and cumbersome. Not everything needs doing inside the Razor engine itself, but in this case, doing it inside the Razor engine and getting it to collapse the whitespace is vastly preferable than the workarounds.

If it's worth doing in Blazor, it's surely worth doing in Razor.