Invalid XHTML markup causes lockup

[csnewman]

Invalid xhtml markup in the form of an unterminated tag causes the CPU to hit 100% and for the page to become completely unresponsive until chrome asks you if you wish to kill the page.

@page "/example"

<h5 class="card-title">(some text)</h5>
<p class="card-text">
    (Some text as well)
<p class="card-text">
   (Some other text)
</p>

As seen, the first p tag is not terminated.

[MitchellEnsink]

The HTML is 100% valid. The closing tag for the P element is optional.

[SteveSandersonMS]

Thanks for reporting this.

We'll change it so that it's a compile error not to have matching tags (XHTML-style). Internally your UI is represented as a tree so it always has to be valid otherwise errors like this can occur. For safety it's best if we reject it at compile time if the developer's intentions are unclear.

[doggy8088]

If <input> tag doesn't have a <input .... /> self-close syntax. The build will failed. I think it maybe the same issue.

[danroth27]

Tracking this with #6217