| 18:11 | <Hixie> | wtf, there's a web events wg? |
| 18:11 | <Hixie> | how many wgs does the w3c need?! |
| 18:13 | <boogyman> | evidently 1 more :-s |
| 18:22 | <zewt> | feels like the first time people set up a web forum |
| 18:23 | <zewt> | and they create 250 little forums that get 2 posts each, and nobody can follow anything |
| 18:59 | <jcranmer> | the W3C will create working groups until they become imposible to number |
| 19:09 | <Ms2ger> | And continue even then |
| 19:57 | <annevk> | Hixie, yeah |
| 19:57 | <annevk> | Hixie, trying to introduce a new init* method |
| 19:57 | <annevk> | I raised some noise, but I'm afraid that's not gonna cut it |
| 19:57 | <annevk> | seems DOM3Events mentioned to get new init* methods introduced in browsers too |
| 20:39 | <Hixie> | annevk: well, just make sure the browser vendors know the specs in question are bogus |
| 20:39 | <Hixie> | annevk: and provide an alternative and make sure that one is the one that gets implemented |
| 20:39 | <Hixie> | annevk: webkit in particular seems to have moved to constructors everywhere |
| 20:39 | <Hixie> | annevk: and i dropped the init*s from the specs i edit |
| 20:40 | <Hixie> | (and moved my timeline for doing that up mostly because of pressure from them) |
| 23:27 | <jarek> | Hi |
| 23:27 | <jarek> | why manifest.appcache gets cached by the browser even if I had not listed it? |
| 23:28 | <jarek> | is this by design? |
| 23:28 | <jarek> | I can reproduce this on Chrome, looks like serious flow |
| 23:28 | <jarek> | s/flow/flaw |
| 23:29 | <jarek> | https://developer.mozilla.org/en/Offline_resources_in_Firefox#section_11 |
| 23:30 | <jarek> | "it is a good idea to set expires headers on your web server for *.appcache files to expire immediately to avoid the risk of caching the manifest files." |
| 23:30 | <jarek> | why would anyone want to cache the .appcache file itself? |