Never cared for hgroup element much anyway. A more useful element would be <byline> or somesuch to identify any Hx-level subtext.
3
@mollydotcom all the <hx> tags can bite me. we just need <h> and css pseudo classes that understand sectioning depth.
2
1
@chriseppstein @mollydotcom That was one thing I actually liked about XHTML 2.0. HTML5's outline algorithm + <hx>s is a real mess, IMO.
1
@jordangray @mollydotcom The sectioning algorithm is fine. I think it could be very useful.
1
@chriseppstein @mollydotcom It strikes me as a bit capricious at times. I find it easier to construct predictable outlines with <hx>.
1
@jordangray @mollydotcom that misses a huge use case for authoring content that can be portable to different documents w/o change. E.g. CMS
2
@chriseppstein @jordangray Portability of content is part of good engineering practices in open tech anyway. That's in part why it's OPEN ;)
Dec 8, 2012 · 7:27 AM UTC


