hugo_stats.json: bad tag if html element contains tab character

[yaaax]

What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.82.0+extended darwin/amd64 BuildDate=unknown

Does this issue reproduce with the latest release?

Yes

Description

Steps to reproduce

1. One markdown file needs to contain an HTML element (e.g. form) declared on several lines, with tabs for indentation, as this example:

<form
	action="[URL]"
	method="post"
>

## Random markdown content
Foo bar

2. Run hugo server -e production

Expected:

Tag "form" should be added within the list of tags within hugo_stats.jsonfile.

Actual:

Tag "form\n\taction=\"[URL]\"\n\tmethod=\"post\"" is added within the list of tags in hugo_stats.json file.

Note:

The issue does not happen if the form is declared in one line :

<form action="[URL]" method="POST">

Similar issue already raised here: #7958
Maybe also related to #8396

[jmooring]

I am unable to reproduce the problem.

git clone --single-branch -b hugo-github-issue-8417 https://github.com/jmooring/hugo-testing hugo-github-issue-8417
cd hugo-github-issue-8417
hugo
cat hugo_stats.json

Also, according to the CommonMark specification, an HTML block must be followed by a blank line. That is why the page renders incorrectly. You can try it here.

[yaaax]

Thanks @jmooring for your advice regarding the blank line.

I've managed to reproduce the issue with tabs instead of spaces for indentation.

Note: I'm not sure if it's a good practice or not 🤔
I personally prefer tab vs spaces for indentation, in general, that's why I've set up prettier to format my files that way.. but there might by something wrong here?

[jmooring]

Thank you. I've update the minimal reproducible example, and the title of this issue. The simplest failing example is:

<hr[TAB]id=a>

The CommonMark specification provides many examples of using tabs for indentation, so your preference is technically sound.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.