I reported this about a year ago and was hoping since we are in the beta stages with 22 it might get fixed.
Basically, the "comment" command will destroy HTML code by misplacing the start/end of comment characters. It's a little tricky to reproduce so I'll try to post the same instructions.
It has to do with tab settings and HTML formatter settings.
With a fresh config, go to Document/HTML options/Formatting, then Edit the profile and set Indent, Org tab size and tab size to 3. Also check Indent with tabs.
Create a new html file with the following:
<html lang="en">
<head>
<meta charset="UTF-8">
<title></title>
</head>
<body>
<div>
<table>
<tr>
<td></td>
</tr>
</table>
</div>
</body>
</html>
You can maybe try using the beautify command as I'm not sure how the forum post will copy over... hopefully then you will see the tr and td lines indented with two tabs at 3 spaces. Now issue the "comment" command on one or more of these lines. I am seeing SE corrupt or destroy the beginning and/or end of the code on these lines when commenting. I'll try posting the results of commenting all lines between the body tags here in a code block...
<html lang="en">
<head>
<meta charset="UTF-8">
<title></title>
</head>
<body>
<!--<div>-->
<!--<table>-->
<!-- <-->
<!-- <td></-->
<!-- </-->
<!--</table>-->
<!--</div>-->
</body>
</html>
I think in other experiments I used 4,3, and 2 space settings and they all corrupted the code too.
As you might imagine, this bug has caught me off guard many times where I've had to go back and repair the "uncommented" code.
Basically it just looks like SE is miscalculating the start/end of the code to insert the <!-- and --> sequences.
Since I work as a web app developer I really hope this one can get fixed...it's a really annoying one.
For the second bug, it's easy to reproduce (and still appears to be there):
* Go to the last line of this HTML file and issue the command "slick-enter". With the latest v22B2, I see the error "VSCFGP_BEAUTIFIER_FUNCALL_PARAM_ALIGN not valid". Maybe this is not supposed to be a valid command for html files, but I tried with other file types and it doesn't happen. Not a big priority; I think I had a macro file back then that triggered this problem so I just worked around it. I am just mentioning it again.