00:52
<MikeSmith>
innovati: you’re not going to have any issues with CSS styling. That video-container element will be parsed into that DOM and be styleable just like any other standard element
01:26
<innovati>
thanks :D
13:22
<gsnedders>
Oh fun, we have loads of tests with <link rel=help> pointing at http://www.w3.org/TR/2013/WD-html-templates-20130214/. Metadata in tests is great, because it's never outdated.
15:19
<annevk>
gsnedders: hmm, I can PR that I suppose
15:19
<gsnedders>
I mean, it's not really worth anyone's time IMO
15:19
<gsnedders>
it's just further evidence that adding loads of metadata is pointless because nobody maintains it
15:21
<MikeSmith>
it would be useful if we used other systems that consumed that data and did something valuable with it
15:21
<MikeSmith>
which we don’t
15:22
<MikeSmith>
and in fact the trend seems to be toward doing the opposite thing and linking from the specs to the test cases instead
15:22
<MikeSmith>
e.g., using <wpt> in Bikeshed
15:23
<gsnedders>
but even having other systems doesn't matter, given we see enough cases in CSS where nobody bothers to update stuff
15:24
<MikeSmith>
I didn’t actually know that was the case for CSS ー that even they weren’t keeping that metadata up to date
15:25
<gsnedders>
I mean, people basically care at the time when preparing an IR to advance to PR, and never otherwise.
15:25
<gsnedders>
Which is my experience in general.
15:25
<MikeSmith>
anyway, not surprised that nobody keeps something up to date ー same old thing of, if not keeping it up to date doesn’t break anything, then nobody is ever going to get alerted that it’s gone out of date
15:25
<gsnedders>
Almost all the cases I've seen of metadata in tests around the W3C it's only ever been properly maintained for PR advancement, and never otherwise, even if the tests are.
15:26
<gsnedders>
Because the vast majority of metadata only has much value for PR
15:26
<MikeSmith>
well seems like the tests get neglected after that too
15:26
<MikeSmith>
Mission Accomplished