The automatic update is still broken and, for once, it's not even my fault!
The resource-timing spec has a clunky history because:
the spec started without levels, so resource-timing;
then moved to levels, with resource-timing-1 redirecting to resource-timing-1 and then to resource-timing-2
then dropped levels recently, so both resource-timing-1 and resource-timing-2 now redirect to resource-timing
With the new redirects and related information in tr.rdf, the W3C script goes berserk, destroys part of the history and creates an infinite loop, which crashes tests and thus prevents further automatic updates.
To avoid this, this update makes resource-timing the main entry point with the whole history, with levels as aliases of resource-timing.
This should unblock the generation and make the W3C script happy again.
The automatic update is still broken and, for once, it's not even my fault!
The resource-timing spec has a clunky history because:
resource-timing;resource-timing-1redirecting toresource-timing-1and then toresource-timing-2resource-timing-1andresource-timing-2now redirect toresource-timingWith the new redirects and related information in
tr.rdf, the W3C script goes berserk, destroys part of the history and creates an infinite loop, which crashes tests and thus prevents further automatic updates.To avoid this, this update makes
resource-timingthe main entry point with the whole history, with levels as aliases ofresource-timing.This should unblock the generation and make the W3C script happy again.