05:09
<annevk>
zcorpan: you should probably comment on http://dev.w3.org/csswg/css-fonts/#object-model and try to fight against useless interfaces like "CSSFontFeatureValuesRule"
05:09
<annevk>
zcorpan: might as well just expose it as a CSSRule for now
05:42
<annevk>
Planning travel is the worst thing. It's great to see the world, but committing to a set of days and particular flights upfront...
08:20
<zcorpan>
annevk: i agree that the design for CSSRule seems weird. i'll ponder what it should be like instead, if it's worth changing it
08:22
<annevk>
zcorpan: so we can't change CSSRule, but we can avoid introducing new crappy string-based APIs in CSS
12:09
<oal>
Is there a document with all valid html tags, and the attributes and attribute values they take?
12:10
<oal>
Preferably json or something I can parse easily
12:11
<webben>
oal: mmm well i think the validator still uses a relaxng schema of some sort
12:13
<oal>
webben, hmm, no way of grabbing that somehow?
12:14
<jgraham>
What do you mean "attributes and attribute values they take"?
12:14
<oal>
I was thinking about scraping http://www.w3.org/TR/html-markup/elements.html, if nothing else is available
12:14
<jgraham>
There can be rather complex rules that can't be expressed in a schema
12:14
<oal>
jgraham, style, type etc
12:14
<oal>
ok
12:16
<oal>
Scraping the w3.org page above should be enough then. At least I get all available tags, and which ones are form related :)
12:24
<Ms2ger>
Keep in mind that scraping the w3.org page probably isn't kosher from a copyright POV
12:24
<Ms2ger>
whatwg.org/html is fine, though
12:33
<oal>
Ms2ger, thanks for letting me know. I'll use the whatwg one then :)
12:49
<jgraham>
hallvors: Nice
12:57
<Ms2ger>
Mm, tests
13:09
<hallvors>
jgraham: um, thanks - but what? Merging the MS tests? ;-)
13:32
<hallvors>
hmm.. still some bugs in those MS tests :-/
13:43
<jgraham>
hallvors: Yeah
13:45
<hallvors>
send-timeout-events exposes bugs in all browsers it seems
13:46
<hallvors>
I thought my review had been sloppy and the test was buggy, but apparently all implementations get it wrong differently :-p
13:48
<zcorpan>
review welcome :-) http://lists.w3.org/Archives/Public/www-style/2013May/0630.html
13:49
<zcorpan>
have a nice weekend guys. (i'll read the logs if you want to dump comments here)
14:28
<GPHemsley>
hmm... the GIF parser in WebKit shares a common ancestor with the one in Gecko
14:28
GPHemsley
wonders what that means for interop
14:29
<jgraham>
Means that the GIF spec couldn't go to Rec. on the basis of those implementations (if the spec was at the W3C)
14:29
<jgraham>
OTOH Opera/Presto doesn't share image decoders except for WebP
14:34
<GPHemsley>
(and Blink shares ancestor with WebKit, so...)
14:37
<Ms2ger>
"+5 Insightful"
14:37
Ms2ger
remembers the days he read /.
14:47
<GPHemsley>
"GIF is a legacy format; we recommend against generating new images in it." - giflib
15:28
<GPHemsley>
FTW: http://wiki.whatwg.org/wiki/GIF
16:27
<zewt>
i had to create a gif just the other day :|
16:28
<zewt>
because Android's video handling is catastrophically stupid (in native code)
17:27
<GPHemsley>
hmm... renaming usernames on MediaWiki requires an extension
17:27
<zewt>
:|
17:36
<GPHemsley>
annevk: Skimming Fetch, it seems like I might want to use it in mimesniff. Agree?
17:37
<GPHemsley>
annevk: (Any chance you could define "resource"?)
17:44
<GPHemsley>
annevk: "basic fetch" does not seem to allow for custom "about:" URLs; is that intentional?
17:50
<TabAtkins>
annevk: Hm, it's more convenient to make it a custom interface, because then you can attach the rules about what goes inside of it better.
17:51
<TabAtkins>
annevk, zcorpan: But I suggested in the mailing list that it needs to descend from CSSGroupingRule, and then it's done. You get free interface for actual rules.