blocks|key|2920873|text|我不认为这是一个好习惯，因为<!代表像<!DOCTYPE这样的标记声明。因此，您认为它被注释了(好吧…浏览器将尝试解释它)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2920874|即使它没有出现，这似乎也不是注释HTML代码的正确语法。|2920875|entityMap^0|E|2|J|9|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

I don't think this is a good habit to take since <code>&lt;!</code> stands for markup declarations like <code>&lt;!DOCTYPE</code>. Thus you think it's commented (well... browser will try to interpret it). 

Even if it doesn't appear, this seems not to be the correct syntax for commenting HTML code.

blocks|key|2921068|text|HTML5中的注释没有新的标准。唯一有效的注释语法仍然是。来自section+8.1.6+of+W3C+HTML5|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2921069|2921070|+Comments必须以四个字符的序列U%2B003C小于号、U%2B0021感叹号、U%2B002D连字符-减号、U%2B002D连字符-减号(，将<!/div>转换为，正如问题中所述。|2921101|最后，您可能希望其他兼容HTML5的解析器的行为与Chrome相同。|2921102|entityMap|0|LINK|mutability|MUTABLE|url|http://www.w3.org/TR/html5/syntax.html#comments|1|http://www.w3.org/TR/html5/syntax.html#tokenization|2|http://www.w3.org/TR/html5/syntax.html#data-state|3|http://www.w3.org/TR/html5/syntax.html#tag-open-state|4|http://www.w3.org/TR/html5/syntax.html#markup-declaration-open-state|5|http://www.w3.org/TR/html5/syntax.html#bogus-comment-state^0|S|8|13|Q|0|0|0|1|8|1T|4|0|0|0|0|2|0|2G|6|0|0|D|1|0|0|0|I|2|0|0|0|0|B|0|0|0|0|M|3|0|0|0|0|B|0|0|0|0|12|4|0|0|0|1S|0|0|0|0|17|0|G|4|0|0|0|S|5|0|0|5I|3|0|8|G|R|K|1D|7|1N|B|0|0^^$0|@$1|2|3|4|5|6|7|2I|8|@$9|2J|A|2K|B|C]]|D|@$9|2L|A|2M|1|2N]]|E|$]]|$1|F|3|-4|5|6|7|2O|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|2P|8|@$9|2Q|A|2R|B|J]|$9|2S|A|2T|B|C]]|D|@]|E|$]]|$1|K|3|-4|5|6|7|2U|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|2V|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|2W|8|@$9|2X|A|2Y|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|2Z|8|@$9|30|A|31|B|C]]|D|@]|E|$]]|$1|Q|3|R|5|6|7|32|8|@]|D|@$9|33|A|34|1|35]]|E|$]]|$1|S|3|-4|5|6|7|36|8|@]|D|@]|E|$]]|$1|T|3|U|5|V|7|37|8|@]|D|@$9|38|A|39|1|3A]]|E|$]]|$1|W|3|-4|5|6|7|3B|8|@]|D|@]|E|$]]|$1|X|3|Y|5|6|7|3C|8|@]|D|@]|E|$]]|$1|Z|3|10|5|6|7|3D|8|@$9|3E|A|3F|B|J]]|D|@]|E|$]]|$1|11|3|12|5|6|7|3G|8|@]|D|@]|E|$]]|$1|13|3|-4|5|6|7|3H|8|@]|D|@]|E|$]]|$1|14|3|15|5|V|7|3I|8|@]|D|@$9|3J|A|3K|1|3L]]|E|$]]|$1|16|3|-4|5|6|7|3M|8|@]|D|@]|E|$]]|$1|17|3|Y|5|6|7|3N|8|@]|D|@]|E|$]]|$1|18|3|19|5|6|7|3O|8|@$9|3P|A|3Q|B|J]]|D|@]|E|$]]|$1|1A|3|1B|5|6|7|3R|8|@]|D|@]|E|$]]|$1|1C|3|-4|5|6|7|3S|8|@]|D|@]|E|$]]|$1|1D|3|1E|5|V|7|3T|8|@]|D|@$9|3U|A|3V|1|3W]]|E|$]]|$1|1F|3|-4|5|6|7|3X|8|@]|D|@]|E|$]]|$1|1G|3|1H|5|6|7|3Y|8|@$9|3Z|A|40|B|J]]|D|@]|E|$]]|$1|1I|3|1J|5|6|7|41|8|@]|D|@]|E|$]]|$1|1K|3|1L|5|6|7|42|8|@]|D|@]|E|$]]|$1|1M|3|1N|5|6|7|43|8|@$9|44|A|45|B|J]]|D|@]|E|$]]|$1|1O|3|1P|5|6|7|46|8|@$9|47|A|48|B|C]]|D|@]|E|$]]|$1|1Q|3|-4|5|6|7|49|8|@]|D|@]|E|$]]|$1|1R|3|1S|5|V|7|4A|8|@]|D|@$9|4B|A|4C|1|4D]]|E|$]]|$1|1T|3|-4|5|6|7|4E|8|@]|D|@]|E|$]]|$1|1U|3|1V|5|6|7|4F|8|@$9|4G|A|4H|B|C]]|D|@]|E|$]]|$1|1W|3|1X|5|6|7|4I|8|@$9|4J|A|4K|B|C]|$9|4L|A|4M|B|C]|$9|4N|A|4O|B|C]|$9|4P|A|4Q|B|C]]|D|@]|E|$]]|$1|1Y|3|1Z|5|6|7|4R|8|@]|D|@]|E|$]]|$1|20|3|-4|5|6|7|4S|8|@]|D|@]|E|$]]]|21|$22|$5|23|24|25|E|$26|27]]|28|$5|23|24|25|E|$26|29]]|2A|$5|23|24|25|E|$26|2B]]|2C|$5|23|24|25|E|$26|2D]]|2E|$5|23|24|25|E|$26|2F]]|2G|$5|23|24|25|E|$26|2H]]]]

There is no new standard for comments in HTML5. The only valid comment syntax is still <code>&lt;!-- --&gt;</code>. From <a href="http://www.w3.org/TR/html5/syntax.html#comments" rel="noreferrer">section 8.1.6 of W3C HTML5</a>:
<blockquote>
Comments must start with the four character sequence U+003C LESS-THAN SIGN, U+0021 EXCLAMATION MARK, U+002D HYPHEN-MINUS, U+002D HYPHEN-MINUS (<code>&lt;!--</code>).
</blockquote>
The <code>&lt;!</code> syntax originates in SGML DTD markup, which is not part of HTML5. In HTML5, it is reserved for comments, CDATA sections, and the DOCTYPE declaration. Therefore whether this alternative is bad practice depends on whether you consider the use of (or worse, the dependence on) obsolete markup to be bad practice.
Validator.nu calls what you have a &quot;Bogus comment.&quot; — which means that it's treated like a comment even though it's not a valid comment. This is presumably for backward compatibility with pre-HTML5, which was SGML-based, and had markup declarations that took the form <code>&lt;!FOO&gt;</code>, so I wouldn't call this new. The reason they're treated like comments is because SGML markup declarations were special declarations not meant to be rendered, but since they are meaningless in HTML5 (with the above exceptions), as far as the HTML5 DOM is concerned they are nothing more than comments.
The following steps within <a href="http://www.w3.org/TR/html5/syntax.html#tokenization" rel="noreferrer">section 8.2.4</a> lead to this conclusion, which Chrome appears to be following to the letter:
<ol>
<li><a href="http://www.w3.org/TR/html5/syntax.html#data-state" rel="noreferrer">8.2.4.1 Data state</a>:
<blockquote>
Consume the next input character:
&quot;&lt;&quot; (U+003C) 
Switch to the tag open state.
</blockquote>
</li>
<li><a href="http://www.w3.org/TR/html5/syntax.html#tag-open-state" rel="noreferrer">8.2.4.8 Tag open state</a>:
<blockquote>
Consume the next input character:
&quot;!&quot; (U+0021) 
Switch to the markup declaration open state.
</blockquote>
</li>
<li><a href="http://www.w3.org/TR/html5/syntax.html#markup-declaration-open-state" rel="noreferrer">8.2.4.45 Markup declaration open state</a>:
<blockquote>
If the next two characters are both &quot;-&quot; (U+002D) characters, consume those two characters, create a comment token whose data is the empty string, and switch to the comment start state.
Otherwise, if the next seven characters are an ASCII case-insensitive match for the word &quot;DOCTYPE&quot;, then consume those characters and switch to the DOCTYPE state.
Otherwise, if there is an adjusted current node and it is not an element in the HTML namespace and the next seven characters are a case-sensitive match for the string &quot;[CDATA[&quot; (the five uppercase letters &quot;CDATA&quot; with a U+005B LEFT SQUARE BRACKET character before and after), then consume those characters and switch to the CDATA section state.
Otherwise, this is a parse error. Switch to the bogus comment state. The next character that is consumed, if any, is the first character that will be in the comment.
</blockquote>
Notice that it says to switch to the comment start state only if the sequence of characters encountered is <code>&lt;!--</code>, otherwise it's a bogus comment. This reflects what is stated in section 8.1.6 above.
</li>
<li><a href="http://www.w3.org/TR/html5/syntax.html#bogus-comment-state" rel="noreferrer">8.2.4.44 Bogus comment state</a>:
<blockquote>
Consume every character up to and including the first &quot;&gt;&quot; (U+003E) character or the end of the file (EOF), whichever comes first. Emit a comment token whose data is the concatenation of all the characters starting from and including the character that caused the state machine to switch into the bogus comment state, up to and including the character immediately before the last consumed character (i.e. up to the character just before the U+003E or EOF character), but with any U+0000 NULL characters replaced by U+FFFD REPLACEMENT CHARACTER characters. (If the comment was started by the end of the file (EOF), the token is empty. Similarly, the token is empty if it was generated by the string &quot;<code>&lt;!&gt;</code>&quot;.)
</blockquote>
In plain English, this turns <code>&lt;!div displayed&gt;</code> into <code>&lt;!--div displayed--&gt;</code> and <code>&lt;!/div&gt;</code> into <code>&lt;!--/div--&gt;</code>, exactly as described in the question.
</li>
</ol>
On a final note, you can probably expect other HTML5-compliant parsers to behave the same as Chrome.

Recently I found that there is, possibly, a new way of commenting in HTML5.

Instead of the typical <code>&lt;!-- --&gt;</code> multi-line commenting I've read about, I thought I noticed that my IDE made a regular <code>&lt;!div &gt;</code> commented out. So I tested it out, and to my surprise Chrome had commented out that tag. It only commented out the tag and not the contents of the div, so I had to comment out the closer <code>&lt;!/div&gt;</code> to avoid closing other divs.

I tested another and it appears that generally putting an exclamation marker in front of the opening of any tag, this symbol <code>&lt;</code>, makes that tag commented out. 

Is this actually new? Is it bad practice? It is actually very convenient, but is it practical yet(if not new)? 

Edit extra details:
Although a syntax error or misinterpretations of this particular syntax is a good reason, how come Chrome actually renders them as full comments? 

The code is written as:

<pre><code>&lt;!div displayed&gt; some text here that is still displayed &lt;!/div&gt;
</code></pre>

And then it is rendered as:

<pre><code>&lt;!--div displayed--&gt; some text here that is still displayed &lt;!--/div--&gt;
</code></pre>

Does HTML5 change the standard for HTML commenting?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

最近，我发现在HTML5中可能有一种新的评论方式。与我读到的典型的多行注释不同，我认为我注意到我的集成开发环境注释掉了一个常规的<!div >。所以我测试了一下，令我惊讶的是，Chrome已经注释掉了这个标签。它只注释掉了标签，而没有注释掉div的内容，所以我不得不注释掉closer <!/div>，以...

问HTML5是否改变了HTML注释的标准？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问HTML5是否改变了HTML注释的标准？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问HTML5是否改变了HTML注释的标准？
EN