| 10:05 | <annevk> | and non-liveness strikes again: http://www.ietf.org/mail-archive/web/websec/current/msg00851.html |
| 10:06 | <annevk> | maybe we should keep some kind of wiki page |
| 11:22 | <Velmont> | annevk: I printed the XHR2 non-dev version at first, but that was because I was noob and noone told me I should read the dev version :P (odinho btw) |
| 11:23 | <Velmont> | I became quite confused when what I read on paper didn't match what I was reading on the screen (at that point I had learned to use the dev version) |
| 11:23 | <annevk> | Velmont: heh |
| 11:23 | <annevk> | Velmont: I guess XHR needs a notice similar to http://www.w3.org/TR/html5/ |
| 12:48 | <jgraham> | Also, it should have a print stylesheet that replaces the content of the spec with the friendly message "Seriously?" |
| 17:01 | <jarek> | should single invalid selector make the whole @keyframes rule invalid? |
| 17:01 | <jarek> | this is what happens on Chrome |
| 17:01 | <jarek> | but the spec does not mention it |
| 17:02 | <jarek> | I would expect the declaration block with invalid selector to be skipped, not the whole atrule |