# [02:38] <Hixie> heycam: regarding the style sheet, i really don't want to go there. historically, we've had problems whenever specs don't stick closely to the official style sheet (e.g. CSS1's marble background). It also dilutes the W3C brand if the specs have different styles. I would recommend instead asking the pubteam to update their styles, so that all specs could benefit, not just hmtl.

# [10:34] <hsivonen> annevk: so is the policy for HTML4 features checking the level of complaints?

# [10:35] <Hixie> that isn't the criteria for any feature, as far as i'm concerned

# [10:36] <jwalden> annevk: dunno if you can answer, but why doesn't 10a1 include <video> support? there was a test build way back that did support it, and I was surprised to see it gone when I picked up 10a1 recently

# [10:37] <annevk> jwalden, our test build only had the simple features, not the advanced API

# [11:10] <jgraham> Although I guess there might be a strong correlation with people interested in reading the HTML5 spec

# [11:13] <Lachy> the other issue is that letting authors specify aural presentation isn't likely to end up with great results because the vast majority have very little understanding of the concepts involved and are unlikely to know enough to specify appropriate values

# [11:14] <Lachy> it's better to leave such things to the experienced people developing the text to speech systems

# [16:56] <Lachy> that doesn't appear to have collected any data on class and id values

# [16:56] <jgraham> gsnedders: html5lib seems to mostly work in python 3 for some definition of mostly which means "all the bits I cared enough to get working and only if you don't do certian things like try to pass it a file not opened in binary mode"