| 00:30 | <MikeSmith> | annevk: thanks, taking a look right now |
| 00:33 | <frewsxcv> | does anyone know why the webidl spec doesn't mention the [[OwnPropertyKeys]] binding in this section? https://heycam.github.io/webidl/#ecmascript-binding |
| 00:58 | <MikeSmith> | annevk: fwiw (and unrelated to what you pinged me about) I like "syntax violation" but I think optimally we should maybe align the language for this "parse error" stuff across all specs, including the HTML spec, but in the HTML spec, since the tree-construction algorithm also contains "parse error" cases, "syntax violation" may not work for those cases |
| 05:12 | <annevk> | MikeSmith: isn't anything in the tree builder ultimately a syntax violation? |
| 05:13 | <annevk> | MikeSmith: nothing there is about semantics as far as I know |
| 05:14 | <annevk> | frewsxcv: maybe it's never modified? |
| 05:16 | <MikeSmith> | annevk: yeah especially after looking through a few of the cases in the tree-builder part, I think "syntax violation" would work for those too |
| 05:16 | <frewsxcv> | annevk: what is 'it' referring to? |
| 05:16 | <MikeSmith> | annevk: I had in my mind that some of them were more like lexical violations but I guess that's splitting hairs anyway |
| 05:16 | <annevk> | frewsxcv: [[OwnPropertyKeys]] |
| 05:17 | <frewsxcv> | It should get used for 'supported property names', right? |
| 05:19 | <annevk> | frewsxcv: are those not stored directly on the object? |
| 05:19 | <annevk> | frewsxcv: so that [[OwnPropertyKeys]] does the right thing? |
| 05:21 | <frewsxcv> | annevk: 'those'? |
| 05:21 | <annevk> | frewsxcv: https://heycam.github.io/webidl/#dfn-named-property-visibility |
| 05:26 | <frewsxcv> | The implementation for Object.getOwnPropertyNames has different implementation rules for different html collections based on the 'supported property names'. |
| 05:26 | frewsxcv | is struggling to stay awake....he's going to go to sleep |
| 13:53 | <Domenic> | Web IDL was largely written in ES5 era. I am not sure [[OwnPropertyKeys]] existed then. |
| 15:31 | <jojo-> | anyone here of the ppl who authored the appcache part of the html5 spec? |
| 15:36 | <annevk> | jojo-: that'd be Hixie, but he's not around much |
| 15:36 | <jojo-> | annevk: yeah, i figured. i sent an email to him a few days back but haven't gotten a reply yet. guess he's really busy |
| 15:37 | <annevk> | jojo-: the plan is to remove the appcache section and remove support from browsers |
| 15:37 | <jojo-> | lol, what? really? |
| 15:37 | <jojo-> | and why? |
| 15:37 | <annevk> | jojo-: if you want something changed in the HTML Standard best is probably to file a bug or email whatwg⊙wo |
| 15:37 | <jojo-> | and what's gonna replace that functionality |
| 15:37 | <annevk> | jojo-: service workers |
| 15:37 | <jojo-> | hmkay, haven't really looked into it yet to be honest |
| 15:38 | <jojo-> | annevk: where would one get that kind of information? is that something discussed on the public whatwg mailing list? |
| 15:38 | <annevk> | jojo-: yeah and public-webapps⊙wo to some extent |
| 15:39 | <annevk> | jojo-: you can also learn a fair bit by following developer advocates on Twitter, not sure there's really one canonical source |
| 15:39 | <jojo-> | so will this be dropped like a hot iron or "phased out / deprecated" with support still lingering in browsers? |
| 15:39 | <annevk> | jojo-: ideally we would've updated the HTML Standard a while ago with this information |
| 15:39 | <annevk> | jojo-: if browsers don't drop support we won't drop it from the spec |
| 15:39 | <annevk> | jojo-: but browsers have plans to remove support |
| 15:40 | <jojo-> | ok, gotta do some more googling then i suppose |
| 15:40 | <jojo-> | guess i'll stay in this channel for the foreseeable future though ;) |
| 15:41 | <annevk> | jojo-: you should be able to get information on various specs here, especially those pertaining to browsers |
| 15:42 | <jojo-> | cool |
| 15:42 | <jojo-> | are you writing the specs as well? |
| 15:43 | <annevk> | yup |
| 15:43 | <annevk> | https://wiki.whatwg.org/wiki/User:Annevk keeps track somewhat |
| 15:46 | <jojo-> | thanks. i saw that wiki before but didn't browse the userpages |
| 17:20 | <Domenic> | Hmm I did not know that Fetch was formerly CORS. |
| 17:57 | <jojo-> | is there some good guide on how browser caching is implemented in different browser and when the cache is cleared? |
| 19:47 | <jojo-> | so, may be an old hat for you guys, but nevertheless: https://heipei.github.io/2015/08/20/Persistent-AppCache-Injections/ |
| 20:17 | <Domenic> | botie: tell Ms2ger please review https://github.com/w3c/web-platform-tests/pull/2085 to make sure I am not insane |
| 20:17 | <botie> | will do |
| 21:26 | <botie> | Ms2ger, at 2015-08-16 20:17 UTC, Domenic said: please review https://github.com/w3c/web-platform-tests/pull/2085 to make sure I am not insane |
| 21:27 | <Ms2ger> | Domenic, seems possible, will look in the morning |
| 22:09 | <Domenic> | Trying to get the web platform tests to pass has led to a bunch of discoveries |
| 23:34 | <Sebmaster> | annevk: i somehow can't parse the sentence/conditions at https://url.spec.whatwg.org/#file-state > otherwise > 1; what's the intent there? |