我只是好奇在锚标记的 title 属性或 img alt 属性中使用 html 字符实体是否会被拒绝？我使用 jQuery 从属性中提取/放置信息，并且在此应用程序中以这种方式应用格式非常方便
<em>TEXT</em>
- 例如，在标题属性内。它似乎验证得很好，但由于某种原因感觉有点脏。感谢您在这里提供任何反馈。
I'm just curious if it's in any way frowned upon to use html character entities in the title attribute of an anchor tag or in the img alt attribute? I'm using jQuery to pull/place info from the attributes, and it's very convenient in this application to apply formatting in this way--
<em>TEXT</em>
--within the title attribute, for example. It seems to validate just fine but feels a little dirty for some reason. Thanks for any feedback here.
发布评论
评论（3）
我觉得有点乱。任何需要您将数据存储在 HTML 属性中（用于其他用途）的插件都是糟糕的插件。
标题标签应该包含一个简单明了的描述性标题。
使用 $.data 代替或 html5 数据属性。更好的是，该插件应该允许您传递任何值或函数，然后从那里开始。
It seems a bit messy to me. Any plugin that requires you to store data in a HTML attribute that was meant for something else, is a bad plugin.
The title tag is supposed to include a descriptive title, plain and simple.
Use $.data instead or html5 data attributes. Better yet, the plugin should allow you to pass any value or a function, and go from there.
不，不是。
另一方面，使用字符绘制装饰箭头是。它们看起来很奇怪，用屏幕阅读器阅读时，听起来更奇怪。
这很好，只要您记住属性的存在是有目的的，并且您将它们用于该目的而不是作为一般数据存储。
如果您想要通用数据存储，则 HTML 5 有
data-*No, it isn't.
Using characters to draw decorative arrows, on the other hand, is. They look weird and, when read with a screen reader, sound even weirder.
That's fine, so long as you remember that the attributes are there for a purpose and you use them for that purpose and not as a general data store.
If you want a general data store then HTML 5 has
data-*一点也不。 Html 实体只是一种对可能被解析器混淆的字符或未出现在 ASCII 集中的字符（如 3/4）进行编码的方法。
Not at all. Html entities were simply a way to code-ify characters that could be confused by the parser, or characters that did not appear in the ASCII set, like 3/4.