</textarea> doesn’t align

[PhilippJR]

It is a Blazor Wasm app.
I created a brand new repo. Please simply clone it, find the following code in Home.razor and hit CTRL+K,D. Among other things, you will see that </textarea> is not being aligned properly.

@* CTRL+K,D indents this comment and the "div", misaligns "oninput", does not align "</textarea>" and does not align the closing "</div>" with the opening "<div>". *@
<div>
    <textarea id="foobarbaz"
              disabled="@(!_bool3)"
              @bind="MyString"
              oninput="if(this.value.includes('\n')) foobarbaz.blur()">
                            </textarea>
</div>

According to @davidwengier

Indenting comment, and “div” and “oninput” [...] seems to be fixed after recent updates. [...] The “</textarea>” doesn’t align is actually by design. The formatter treats the entire contents of a textarea or pre tag as having significant whitespace, and so purposefully doesn’t touch these. I could definitely see this one being debatable, so feel free to log an issue on our repo to change this behaviour..

Source

OS: 10.0.26200.0, VS: 18.5.1 (18.5.11716.220), Product: professional-2026, Project type: C# / Razor editor

[davidwengier]

To expand on what I meant a little, given this snippet of Html:

<div>
    <textarea id="textarea1">
        Hello
                            </textarea>
</div>

<div>
    <textarea id="textarea2">
        Hello
    </textarea>
</div>

textarea1.value.length is 42, and textarea2.value.length is 18. So whilst it definitely looks better, and there is possibly (hopefully?) nobody relying on this behaviour, if the Razor formatter were to move the close textarea tag, it would strictly speaking change the behaviour of the page at runtime, which is a bit of a no-no for formatting. At least not without a decent community sentiment that it's okay.

[PhilippJR]

Oh, thanks for clarification. I actually hadn't realized that.
But isn't that also true for a ? I mean, replacing the textarea by a span, span1.textContent.length returns 36. After CTRL+K,D it returns 21. I now, it is not critical with spans, but technically CTRL+K,D changes the output.

[davidwengier]

You are 100% correct, but in my mind at least, Ctrl+K,D changing the output of the page is expected. Changing the behaviour of form fields feels different to me. It seems much less likely that the contents of a span will end up in a database somewhere :)

[Elhacen18]

Hi @davidwengier , I'd like to work on this. Format the closing </textarea> tag while preserving inner content whitespace.