Re: Allowing nested <time> elements.

Ian Devlin <>, 2015-07-03 12:13 +0200:
> Archived-At: <>
> There is, apparently, a constraint on the <time> element that forbids them
> from being nested. This constraint is not mentioned in the specification
> itself but I did find it mentioned in an old, out of date, document (
> The W3C
> validator also marks nested <time> elements as an error.
> Does anyone know why this constraint was added?

Hixie added that constraint in 2009 and then
dropped it in 2011 when he briefly replaced the
<time> element with the <data> element. A couple weeks later, he re-
introduced a different <time> element that didn’t
have that same constraint which the old <time> element had.

> Is it still necessary?

I think it’s not. Otherwise Hixie would have re-specced it with that
constraint when he re-defined it in its current form.

> Or is what I am saying irrelevant, that this contraint has been removed
> from the spec. and the validator has not yet been updated?

The validator hasn’t been updated. I added the code in 2009 to check that
constraint around the same time Hixie initially added the constraint to the
spec. And I haven’t touched that line of the code since.

So thanks for catching it. It’s just a bug in the validator—or was, since
I’ve fixed it just now in
and pushed the fix to


Michael[tm] Smith

Received on Thursday, 9 July 2015 18:08:57 UTC