# [00:14] <Philip`> (I suppose I shouldn't provide an infinite number of URLs in a system that takes a large fraction of a second to generate each page with no caching or anything clever, but still they should be more considerate of bad server design...)

# [01:24] <Philip`> (graph_gen.ml in particular produces the .dot file, based on treeconstructot_spec.ml which is generated by treeconstructor.pl from section-tree-construction.html which is an XMLified version of the section from the HTML5 spec)

# [12:51] <Lachy> I'm trying to find a way to reprhase this requirement in selectors api: "If the user agent also supports some level of CSS, the implementation should support the same set of selectors in both these APIs and CSS."

# [12:52] <Lachy> I want it to say that UAs should support the same selectors, but allow for exceptions in case some selectors are introduced that don't work for CSS, but do for selectors api, or vice versa

# [16:53] <hsivonen> here's an idea for a testing project: extracting all the charset aliases supported by Gecko, generating test pages for each and checking which aliases are actually supported by IE, Safari and Opera

# [16:54] <hsivonen> the aliases for the old Apple encodings seem to be particularly inconsistent in different implementations

# [17:02] <hsivonen> implementations don't agree whether the chaset name for MacUkranian should contain the word ukraine or ukranian, whether there should be the x- prefix and whether there should be a hyphen after mac

# [21:18] <andersca> A browsing context can be associated with an application cache. A child browsing context is always associated with the same browsing context as its parent browsing context, if any.

# [21:18] <andersca> should it be "A child browsing context is always associated with the same application cache..." ?