| 00:16 | <gsnedders> | silverdust: I think something like IE3 or NN3 required the attribute value in full; regardless of what, we're talking twenty year old browsers here |
| 06:27 | <annevk> | Pro tip: don't cut your index finger |
| 06:28 | <annevk> | Such a massive pain with the trackpad |
| 06:33 | <MikeSmith> | annevk: use the other hand… |
| 06:34 | <annevk> | MikeSmith: for some reason I'm used to use my right hand for this, and even though I'm left-handed that feels very unnatural |
| 06:34 | <annevk> | MikeSmith: so I'll use my middle finger to point at things |
| 09:21 | <annevk> | https://djcordhose.github.io/flow-vs-typescript/2016_hhjs.html is pretty interesting |
| 09:21 | <annevk> | Didn't really know Facebook was also into the typing game these days |
| 09:30 | <nox> | Is Flow from Facebook? |
| 09:30 | <nox> | Are they unable to name any programming language with something else than a common word? |
| 09:31 | <annevk> | WHATWG is guilty of that too, so... |
| 09:31 | <nox> | Oh? Which languages? I'm curious. |
| 09:31 | <nox> | I was thinking of their ML-like language named Reason. |
| 09:31 | <annevk> | Not languages, but say "Fetch", "Encoding", "Fullscreen", "Notifications", "Streams" |
| 09:32 | <nox> | Mmmh true. I guess I'm less surprised because they are specs. |
| 09:33 | <annevk> | I think generally picking a word is better than picking many words, context is usually sufficient |
| 09:33 | <annevk> | Also, dude, Mozilla named its language Rust |
| 09:34 | <Ms2ger> | Uh,"Go"? |
| 09:43 | <nox> | annevk: Less common than reason and flow. :) |
| 10:08 | <jgraham> | Yeah "Rust Programming" seems reasonably easy to search, "Flow Programming" less so |
| 12:02 | <nox> | https://github.com/w3c/DOM-Parsing/issues/15 |
| 12:04 | <nox> | Also, filed https://github.com/whatwg/html/issues/1394 again. |
| 12:56 | smaug____ | kicks blink and its silly data: handling |
| 13:10 | <smaug____> | hrm, I added a comment to a pull :/ |
| 17:29 | <annevk> | Very happy https://github.com/tc39/ecma262/issues/573 is happening even though I've little to contribute |
| 17:30 | <annevk> | Just feels so good to finally get to the bottom of certain engine disputes, or at least make some progress on them |
| 17:36 | <rodneyre_> | ShadowDOM v1 removed Shadow piercing combinators - http://hayato.io/2016/shadowdomv1/#shadow-piercing-combinators - but https://drafts.csswg.org/css-scoping/#deep-combinator still lists >>> in the static profile -- so what is it now? |
| 17:42 | <annevk> | rodneyre_: I think there's an open issue on this |
| 17:42 | <annevk> | rodneyre_: and some disagreement |
| 17:42 | <annevk> | rodneyre_: see the one on /deep/ |
| 17:44 | <TabAtkins> | rodneyre_: The combinator is *very intentionally* still in CSS in the static profile only (which only covers things like querySelector(), *not* stylesheets). |
| 17:45 | <rodneyre_> | but it won't select into closed shadows, correct? |
| 17:46 | <TabAtkins> | Closed shadows dont' exist yet. (Except handwavey in the form of built-in elements that clearly contain internal structure.) But based on what I think is going to happen, no, it won't select in. It won't give any power that you can't get from just poking via DOM APIs. |
| 17:47 | <Domenic> | closed shadows exist |
| 17:48 | <TabAtkins> | Oh really? News to my ears, but I'm a bit out of the loop. |
| 17:48 | <TabAtkins> | I've stayed in touch *just* enough to figure out what needs to happen on the CSS side. |
| 17:48 | <Domenic> | yeah, they were necessary to get consensus back when that happened. |
| 17:48 | <rodneyre_> | I mean, don't get me wrong. I'd happily do away with that, if we get some way to disable focusable elements within a shadow |
| 17:49 | <annevk> | TabAtkins: I don't think there's agreement on implementing it for querySelector() at this point |
| 17:50 | <TabAtkins> | It's the plan of record to the best of my knowledge, and no one's contradicted it yet. |
| 17:50 | <TabAtkins> | It would be pretty fucking stupid to not have it, given that you can just poke thru via the DOM api. |
| 17:50 | <annevk> | TabAtkins: see https://github.com/w3c/webcomponents/issues/78 |
| 17:51 | <TabAtkins> | Requiring a .query(...).map(x=>x.shadowRoot).query(...) would be dumb as hell just to avoid .query(... >>> ...) |
| 17:51 | <annevk> | It seems fine for a first iteration |
| 17:51 | <TabAtkins> | (It's actually much more difficult to faithfully implement, but even this pretend version is stupid.) |
| 17:51 | <annevk> | It's not even clear you should iterate that way as rniwa points out |
| 18:11 | <Domenic> | Does anyone know the right contact for Gecko for BroadcastChannel? Would be good to get them to weigh in at https://github.com/whatwg/html/issues/1371 |
| 18:11 | <annevk> | Baku |
| 18:11 | <annevk> | bakulf iirc? |
| 18:12 | <annevk> | On GH |
| 18:13 | <Domenic> | https://github.com/bakulf ? |
| 18:23 | <wanderview> | Domenic: I pinged him in IRC as well, although I think this is towards the end of the work day for him |
| 18:43 | <annevk> | Domenic: yeah |
| 20:07 | <zcorpan> | annevk: what happened to your finger? |
| 20:09 | <zcorpan> | hmm i pictured you had it cut off entirely but i suppose that is not necessarily the case |
| 20:25 | <TabAtkins> | I suspect he just cut it, and bandaids make it hard to use touchpads. ^_^ |
| 20:37 | <zcorpan> | just need an outer layer of bacon to fix it 👌 |
| 20:46 | <TabAtkins> | then you get a greasy screen. d- fix |
| 21:56 | <astearns> | kickstarter: conductive bandaids for touchscreen use |
| 21:58 | <jgraham> | astearns: They already exist |
| 21:59 | <astearns> | ugh, of course they do |
| 22:00 | <jgraham> | Your dream of being the Zuckerberg of home medicine will have to be put on hold |