{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 冷血范 的问题《HTML5 Compliant - Trailing Space in Class Attribut》','https://www.manongdao.com/q-351538.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I know that technically HTML5 is a 'living spec' but I'm wondering if it's compliant to have trailing spaces inside of a class name. I didn't see any reference to this scenario in the spec, but one of my teammates said it was invalid. Maybe I missed something?
It'd be a pain to trim those spaces (I'm working inside of a large Java ecom application) and I want to know if it's worth doing for SEO, validation or any other purpose. I get the feeling it's not... haha
According to http://validator.w3.org/ under a
<!DOCTYPE html>the following validates successfully.Leaving a trailing and leading space may be acceptable, but it's not pretty and some people do not consider it to be best a practice.
Anything that knows how to handle class attributes should be fine with this. It is possible to give a tag multiple classes by separating them with spaces so anything which reads them had better know how to deal with spaces.
Yes, it is compliant.
From http://www.w3.org/html/wg/drafts/html/master/dom.html#classes:
From http://www.w3.org/html/wg/drafts/html/master/infrastructure.html#set-of-space-separated-tokens:
As we can see in the link below, there is no restriction on what the developer can use in the class attribute.
http://www.w3.org/html/wg/drafts/html/master/dom.html#classes
In fact, after saying what the classes are and that they're used spliting in the spaces, the author(s) says:
Our colleagues here have tested and it successfully passes W3C validation, so I can't guess why your friend thought it was invalid.