ergophobe - 5:41 pm on Jun 20, 2013 (gmt 0)
Its only stated reason for being in HTML is to support a non essential case in an algorithm that is not implemented in any browser
So since as of March 2013 it was not implemented in any browser, what harm in removing from the spec in April 2013? Because of the millions of webpages that implemented hgroup in anticipation of browser support?
I think this actually illustrates the utility of the Living Standard [webmasterworld.com] approach rather than the pitfall. Rather than waiting for three years while the W3C nabbles about behind closed doors to issue the next version of the spec, while in the meantime browser manufacturers are implementing a useless tag, the spec can see the situation in the real world and adapt based on what actually makes sense.