| 00:43 | <caitp> | you could always require the spambots to pick out photos of specific kinds of boats, to prove they're human |
| 00:43 | <caitp> | anyone willing to actually go through that crap would probably really, really want you do fix their spec issue |
| 00:44 | <Garbee> | "Pick the one called Boaty McBoatFace" |
| 13:16 | <zcorpan> | MikeSmith: are you interested in implementing https://github.com/whatwg/html/pull/1356 for v.nu? would be nice to sanity-check against the test cases |
| 13:17 | MikeSmith | looks |
| 13:17 | <MikeSmith> | I think that might a change to the parser but regardless yeah I would be willing to implement it for testing |
| 13:19 | <zcorpan> | cool |
| 14:20 | <whatwg> | Hey! |
| 14:21 | <whatwg> | First time at IRC |
| 15:18 | <FND> | hi - what's the current status of the Custom Element APIs; can https://github.com/w3c/webcomponents/pull/405 be considered final? |
| 15:20 | <FND> | if so, have polyfill maintainers indicated that they'll update? (AFAIK there's the Polymer-based stuff at webcomponents.org as well as https://github.com/WebReflection/document-register-element) |
| 15:22 | <Domenic> | FND: yes; custom elements have been upstreamed into HTML (and parts into DOM). See https://html.spec.whatwg.org/multipage/scripting.html#custom-elements. I believe Polymer is working on an updated polyfill, although some things are much harder to polyfill in the new version. |
| 15:24 | <FND> | thanks Domenic - can you elaborate on the polyfill difficulties; what will this mean for users? |
| 15:25 | <Domenic> | FND: well, they depend on ES6 class syntax, including aspects that are impossible to transpile in general. So I believe Polymer is investigating things like an extra transpiler pass or advising authors to add an extra line to their constructor (which they won't need in native implementations) in order to work with Polymer. I am not the expert here though; |
| 15:25 | <Domenic> | let me see if I can summon a Polymer person. |
| 15:27 | <FND> | tbh, I'm not actually that interested in Polymer-specific aspects, as I prefer to use vanilla custom elements (is that a term?) |
| 15:27 | <FND> | (though I realize their solution might well be generally applicable) |
| 15:27 | <Domenic> | Yeah, but they maintain a custom elements polyfill |
| 15:27 | <FND> | gotcha |
| 15:28 | <FND> | the ES6 dependency actually sounds promising in a way, as so far Babel and the polyfills (either of them) didn't cooperate |
| 15:28 | <FND> | (Babel injects some sort of class check that fails on HTMLElement, not sure about the details right now) |
| 15:29 | <Domenic> | Yeah, I think the polyfill will involve overwriting window.HTMLElement |
| 15:30 | <Domenic> | FND: OK, so it sounds like the best place to get info about the Polymer custom elements polyfill will be https://groups.google.com/forum/#!forum/polymer-dev or https://polymer-slack.herokuapp.com |
| 15:30 | <Domenic> | It sounds like they're still in the planning stages for the update |
| 15:30 | <FND> | roger, thank you |
| 15:41 | <FND> | FWIW, the Babel vs. polyfill issue is because polyfilled `HTMLElement` is not a constructor, which trips up Babel's inheritance check: |
| 15:42 | <FND> | if (typeof superClass !== "function" && superClass !== null) { throw new TypeError(…) } |
| 15:49 | <FND> | also, in case anyone cares: looks like WebReflection's polyfill _might_ be updated https://github.com/WebReflection/document-register-element/issues/58 |
| 15:58 | <astearns> | trackbot, start meeting |
| 15:58 | astearns | grr |
| 16:55 | <nox> | Does Edge still do www.<actually typed>.com on ctrl-enter in address bar? |
| 19:40 | <smaug____> | I wonder... if page A opens a new window B and B adds event listener to its opener, and then B is closed |
| 19:41 | <smaug____> | GC can't (or at least shouldn't) collect anything from B |
| 19:41 | <smaug____> | (GC or CC or whatever UA has) |
| 20:28 | <Mek> | hmm, without looking at the spec or trying stuff, what would you expect the output of the following code to be: let c = new MessageChannel(); c.port1.onmessage = e => { console.log(e.data); c.port1.close(); }; c.port2.postMessage('foo'); c.port2.postMessage('bar'); |
| 20:55 | <Domenic> | Mek: ignoring my "this is a trick question" instincts, I'd expect 'foo' only |
| 20:55 | <Domenic> | wellll |
| 20:55 | <Mek> | Domenic: both spec and implementation say to print both... |
| 20:55 | <Domenic> | it depends on whether onmessage is async |
| 20:55 | <Domenic> | if it's async i would expect both |
| 20:56 | <Domenic> | basically i expect .close() to be a "graceful close" that allows processing queued up messages |
| 20:56 | <Domenic> | i'm just unclear on whether .close() happens before or after 'bar' gets queued |
| 20:57 | <Mek> | for BroadcastChannel the spec seems to be the same (postMessage synchronously figures out the set of non-closed destinations, and then queues tasks to all of them), but the firefox implementation doesn't behave that way, so I'm trying to figure out if I should file a firefox or a spec bug... |
| 20:58 | <Domenic> | Mehhh... spec bug might get a broader audience of people with expectations, and as a bonus Firefox people will probably show up there anyway? |
| 20:59 | <Mek> | true... |
| 21:29 | <Krinkle> | Hm.. is "The" supposed to fall behind the main title? https://whatwg.org/specs/ |
| 22:29 | <TabAtkins> | Krinkle: I doubt it. ^_^ Domenic annevk |
| 22:30 | <Domenic> | I dunno, looks intentional to me |
| 22:30 | <Domenic> | We can check with Hixie |
| 22:44 | <astearns> | it's just a creatively-kerned "ThWeeb" |
| 22:48 | <terinjokes> | is there a good way to find all the CSS properties that allow url? |
| 22:52 | <Domenic> | There's some CSS index, not sure if it's good for that purpose... |
| 22:53 | <Domenic> | terinjokes: https://drafts.csswg.org/indexes/#properties will get you halfway there, but yeah, not quite what you need |
| 22:53 | <Krinkle> | astearns: Domenic: http://i.imgur.com/DVxSe8z.png |
| 22:53 | <Domenic> | Krinkle: yes, that looks intentional to me. Deemphasizing the pronoun |
| 22:54 | <Krinkle> | k :) |
| 22:54 | <Krinkle> | It most certainly does not read as "ThWeeb" however. |
| 23:06 | <Hixie_> | it's intentional |
| 23:06 | <Hixie_> | also, i have no design sense |
| 23:06 | <Hixie_> | so... |
