| 06:45 | <wycats__> | I don't understand "element in specific scope": http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html#has-an-element-in-the-specific-scope |
| 06:45 | <wycats__> | "If node is the target node, terminate in a match state" |
| 06:45 | <wycats__> | I don't know what the target node is |
| 09:32 | <jgraham> | wycats__: It isn't super-clear, but the "target node" is supposed to be an element of the type that you are searching for |
| 09:34 | <jgraham> | e.g. when it says "has a 'body' element in scope", "target node" is an element named body (I guess it is not 100% clear if that is supposed to be an element in the HTML namespace named body, or any element named body) |
| 09:34 | <jgraham> | (I think someone opened a bug about that) |
| 09:37 | <jgraham> | but basically "if the stack of open elements has an x element in scope" should be read as "if elementInScope(openElements, targetNode=x)" |
| 11:43 | <crocket> | ~school |
| 11:59 | <crocket> | `school |
| 15:24 | <zewt> | heh just saw multipart/x-mixed-replace ... seems pretty nasty, heh |
| 15:25 | <zewt> | since multipart/mixed assumes you have the whole data set in advance to pick a boundary guaranteed not to appear in the data (but academic enough of a problem, I guess) |
| 16:09 | <Mekzholan> | Is here someone I could tell a feature which relating to the applicationCache? |
| 16:09 | <Mekzholan> | I'd love to be able to use partial addresses or wildcards for the CACHE entries, e.g. listing each icon in that file isn't much fun. (It could work by adding wildcarded files to the cache only after they have been used by the page). |
| 16:09 | <Mekzholan> | Alternatively (or even additionally) it would be great to add an applicationCache.add() and applicationCache.remove() method to the API. |
| 16:09 | <Mekzholan> | And perfect would be an API function that forces a discard of the full cache, realoads the manifest and every file in it... |
| 16:11 | <Mekzholan> | -which +whish |
| 16:24 | <matjas> | “The <title> element must not be empty” — http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#the-title-element |
| 16:25 | <matjas> | HTML4 et al. didn’t have such a requirement |
| 21:27 | <MikeSmith> | matjas: Hixie made that change to the criteria for the title element only a couple months or so ago |
| 21:27 | <MikeSmith> | before then even in HTML LS and HTML5, it was allowed to be empty |
| 21:30 | <zewt> | (and it's just conformance criteria) |
| 21:32 | <MikeSmith> | yeah |
| 23:40 | <odinho> | jgraham: I asked GitHub about changing the root of the network, and they said they only needed an email from you if you wanted to do it. (change "main repo" of testharness.js to w3c/testharness.js from jgraham/testharness.js). |
| 23:40 | <odinho> | jgraham: I actually didn't ask for that repository, but another one, but remembered it was more or less the same situation with testharness.js. |
| 23:42 | <gsnedders> | Yeah, getting most things like that changed in Github is really simple, they just need an email asking them to. |