使用未知的HTML标签可以吗?-IsitOKtouseunknownHTMLtags?

13  

You should always approach HTML as it is defined in its respective specification. "Defining" new tags is a bit of an extreme approach. It might pass a browser check because it implements various failsafes, but there is no guarantee of this. You're entering the land of Undefined Behaviour, at best. Not to mention you will fail validation tests, but you seem to be aware of that.

您应该始终接近HTML，因为它是在其各自的规范中定义的。“定义”新标签有点极端。它可能会通过浏览器检查，因为它实现了各种故障保护，但这并不能保证。你正在进入一个行为不明确的世界。更不用说验证测试会失败，但你似乎已经意识到了这一点。

If you wish to be more semantically expressive in your markup, you can use HTML5 which defines quite a bit of more descriptive tags for describing the structure of your page instead of generic divs which need to be appended ids or classes.

如果您希望在标记中更具语义表达性，您可以使用HTML5，它定义了相当多的描述性标记来描述页面的结构，而不是需要附加id或类的通用div。

In the end, a short answer: No, it's bad practice, you shouldn't do it and there could be unforeseen problems later on in your development.

最后，一个简短的回答:不，这是不好的做法，您不应该这样做，并且在以后的开发中可能会出现不可预见的问题。

49  

user1309389 had a very good answer, and I agree with the appeal to the spec. But I disagree with their conclusion, and I think they're wrong about made-up elements leading to "undefined behaviour". I want to propose an alternative way of thinking about it, rooted in how the spec and browsers actually handle made-up elements.

user1309389有一个很好的答案，我同意对spec的要求，但是我不同意他们的结论，我认为他们对导致“未定义行为”的虚构元素的看法是错误的。我想提出一种考虑它的替代方法，其根源在于规范和浏览器实际如何处理虚构的元素。

It's 2015, we're on the verge of the CustomElement spec being widely adopted, and polyfills are readily available. Now is a great time to be wondering about "making up your own elements". In the near future, you'll be able to create new elements with your own choice of tag and behaviour in a fully standard and supported way that everyone can love. But until this lands in all browsers, and until the majority of people are using supporting browsers, you can take advantage of the hard work of the Polymer or X-Tags projects to check out the future of custom elements in a nearly-standard and mostly-supported way that quite a few people can love. This is probably the "right thing" to do. But it doesn't answer your question, and frankly I find "just use X" or "don't do X" to be less helpful than "here's how the spec covers this, and here's what browsers do". So, here's what I love.

现在是2015年，我们正处在被广泛采用的CustomElement规范的边缘，并且polyfill可以很容易地获得。现在正是思考“构建自己的元素”的好时机。在不久的将来，您将能够用您自己选择的标签和行为创建新的元素，以一种所有人都能喜欢的完全标准和受支持的方式。各浏览器,但直到这土地,直到大多数人使用的是支持的浏览器,您可以利用聚合物的努力或X-Tags项目检查自定义元素的未来nearly-standard mostly-supported方式,相当多的人可以爱。这可能是正确的做法。但它并没有回答你的问题，坦率地说，我发现“使用X”或“不使用X”比“规范如何覆盖这一点，以及浏览器如何做”更没有帮助。这就是我喜欢的。

Against the heartfelt recommendation (and sometimes screaming) of much of the web dev community, I've been working with "made-up" elements for the past year, in all of my production projects, without a polyfill, and I've had no unsolvable issues (yet), and no complaints. How? By relying on the standard behaviour of HTMLUnknownElement, the part of the W3C spec that covers the case of "made-up" elements. If a browser encounters an unrecognized HTML element, there is a well-defined and unambiguous way that it should be handled, and HTMLUnknownElement defines that behaviour, and you can build on top of that. HTMLUnknownElement also has to be powerful and correct enough to "not break the web" when encountering all the tags that are now obsolete, like the tag. It's not recommended that you use HTMLUnknownElement, but in theory and in practice, there's absolutely no harm in doing so, if you know what you're doing.

与大多数web开发社区发自内心的推荐(有时是尖叫)相反，我在过去的一年中一直在使用“虚构”元素，在我所有的生产项目中，没有一个polyfill，我也没有任何无法解决的问题(到目前为止)，也没有任何抱怨。如何?通过依赖HTMLUnknownElement的标准行为，W3C规范中涵盖了“虚构”元素的部分。如果浏览器遇到一个未识别的HTML元素，那么应该以一种明确定义的、明确的方式来处理它，并且HTMLUnknownElement定义了这种行为，您可以在此基础上进行构建。HTMLUnknownElement还必须足够强大和正确，才能在遇到现在已经过时的所有标记时“不破坏web”，比如 标记。不建议您使用HTMLUnknownElement，但在理论上和实践中，如果您知道自己在做什么，那么这样做绝对没有害处。

So how does HTMLUnknownElement work? It is just an extension of the HTMLElement interface, which is the standard interface underlying all HTML elements. Unlike most other elements however, HTMLUnknownElement doesn't add any special behaviour — you get a raw element, unadorned with any special behaviour nor constraining rules about use. The HTMLDivElement interface works almost exactly the same way, extending HTMLElement and adding almost no additional behaviour. Put simply, making up your own element is almost identical to using a div or span.

那么htmlunnelement是如何工作的呢?它只是HTMLElement接口的一个扩展，它是所有HTML元素的标准接口。然而，与大多数其他元素不同，HTMLUnknownElement不添加任何特殊行为——您得到的是一个原始元素，没有任何特殊行为的修饰，也没有关于使用的约束规则。HTMLDivElement接口的工作方式几乎完全相同，扩展了HTMLElement并添加了几乎没有额外的行为。简单地说，创建自己的元素几乎等同于使用div或span。

What I like about "making-up" elements is the change of mindset. You should use or invent HTML elements based on several factors, ranging from how clear it makes the markup to read, to how the browser and screen readers and search engines parse your code, to how likely your code is to be "correct" by some objective measure. I sparingly use made-up elements, but I use in exactly the way Richard described, to make things more meaningful for the author of the HTML, not just meaningful to a computer service that extracts metadata. When used in a consistent way across a team, there can be a big benefit since made-up elements can concisely express what they're for.

我喜欢“化妆”元素的是心态的转变。您应该基于以下几个因素来使用或发明HTML元素，从如何清除标记到阅读，到浏览器和屏幕阅读器和搜索引擎如何解析代码，以及您的代码如何通过一些客观的度量来“正确”。我很少使用虚构的元素，但我使用的方式与Richard描述的完全一致，使HTML的作者更有意义，而不仅仅是对提取元数据的计算机服务有意义。当在团队中以一致的方式使用时，会有很大的好处，因为编造的元素可以简洁地表达它们的目的。

I particularly like using made-up elements to indicate when I will be using JS to define extra behaviour for an element. For instance, if I have an element that will have children added/removed by JS, I will use a made-up element as a clue that this element is subject to special behaviour. By the same token, I don't use a made-up element when a standard element will suffice. You will see live happily next to