| 01:37 | <jgraham> | |
| 01:38 | <ato> | A man of few words. |
| 02:45 | <MikeSmith> | heh |
| 02:45 | <MikeSmith> | jgraham: well put |
| 05:02 | <deadowl> | gonna afk for a bit, but was wondering about the concept of providing a source set for scripts. There are multiple CDNs that a web author can hook into for a script (e.g. jquery), and one of those locations may be cached. The default source could otherwise then provide a local (server-wise) copy of the script. |
| 10:00 | <foolip> | zcorpan_: that's interesting. I didn't think to look for CDATA in strings |
| 10:00 | <foolip> | but in the case of xhr.send(document), the problem would happen on the server-side |
| 10:02 | <foolip> | it's possible for the output of innerText and XMLSerializer to be sent over the network as well, of course |
| 10:04 | <zcorpan_> | foolip: you mean innerHTML i guess |
| 10:10 | JakeA | checks channel name, looks for annevk in members list, checks channel name again |
| 11:00 | <foolip> | zcorpan_: yes, innerHTML |
| 11:00 | <foolip> | zcorpan_: https://codereview.chromium.org/756313002/#msg4 |
| 11:00 | <foolip> | would you remove CSSRule.CHARSET_RULE, or leave it like annevk has done for some Node type constants? |
| 11:02 | <zcorpan_> | foolip: i guess leave it |
| 11:05 | <foolip> | zcorpan_: ok, thanks |
| 14:45 | <Ms2ger> | mathiasbynens, wait, we have ipv6 adoption? |
| 14:51 | <mathiasbynens> | Ms2ger: my home connection (Telenet) has supported IPv6 for 6 months now |
| 14:54 | <wanderview> | JakeA: I think annevk is traveling for the moz portland thing this week |
| 14:54 | <JakeA> | wanderview: ahh ok, cheers! |
| 14:55 | <Ms2ger> | I hope he's arrived by now |
| 17:25 | <Domenic> | TabAtkins: can I use https://github.com/tabatkins/bikeshed/pull/288 with the web interface automatically, or does that need to wait for an update? |
| 17:44 | <TabAtkins> | Domenic: It updates regularly and automatically. |
| 17:45 | <Domenic> | TabAtkins: so it automatically adds new command-line params? |
| 17:45 | <TabAtkins> | Ah, that part not so much. We'll need to bug plinss to have pass-through of parameters. |
| 17:47 | <Domenic> | done https://github.com/tabatkins/bikeshed/pull/288#issuecomment-65272321 |
| 19:21 | <TabAtkins> | rubys: For whatever reason, your responses tend to break threading. |
| 19:34 | <IdeaHat> | Hey all. I'm working on a mime-sniffer for the Servo project. Looks like there are bugs in the documentation at https://mimesniff.spec.whatwg.org/, but they also look like they are already red-highlighted. Does that mean they are already noted? |
| 19:35 | <jgraham> | IdeaHat: Yeah, although I don't know if anyone is really working on that spec or not |
| 19:35 | <jgraham> | GPHemsley: ^ |
| 19:37 | <IdeaHat> | jgraham: fair nuff. I was going to also ask, the method for returning the sniffed type is a little vague. We're just writing over the header right now. |
| 19:38 | <IdeaHat> | But if its not currently being maintained I can look else where. |
| 19:40 | <jgraham> | IdeaHat: I don't know if there's anything better than that spec. I kind of lost track tbh. You might need to own the spec if you want it fixed ;) |
| 19:40 | <IdeaHat> | fair nuff... |
| 19:41 | <jgraham> | annevk might know more when he's around |
| 19:43 | <Domenic> | IdeaHat: own the spec ... do it ... join ussss |
| 19:44 | <caitp> | (speaking of that, whatever happened to the window.console spec guy?) |
| 19:44 | <IdeaHat> | hehe, I can't commit at the moment. |
| 19:48 | <Domenic> | terinjokes: yeah, what happened to the console spec |
| 19:49 | <terinjokes> | caitp: i'm still here |
| 19:49 | <terinjokes> | it's on GitHub, we've got a room #console-spec |
| 19:49 | <Domenic> | pssh what's wrong with this room |
| 19:50 | <caitp> | just wanted to see how that was going, and if there's been any movement on unifying them all in browsers |
| 19:50 | <caitp> | not expecting miracles, but you know =) |
| 19:50 | <Domenic> | https://terinjokes.github.io/console-spec/ |
| 19:51 | <Domenic> | not bad, a solid day of effort would make that console.spec.whatwg.org-worthy IMO. |
| 19:51 | <terinjokes> | ocotober! (sigh, need to get back to this) |
| 19:52 | <terinjokes> | two major things right now are defining the logger function, and the special logic for console.table |
| 19:54 | <Domenic> | You could get the script-observable stuff done with almost no work |
| 19:55 | <Domenic> | That probably means just specifying what assert() does (I think it throws?) and putting in warning notes about the non-interoperable aspects of the IDL. |
| 19:57 | <terinjokes> | Domenic: pardon, script observable? |
| 19:57 | <Domenic> | terinjokes: basically, testable using JS instead of human eyes |
| 19:58 | <Domenic> | terinjokes: to be interoperable with web content a browser only needs to implement script-observable parts |
| 19:58 | <Domenic> | to be developer-friendly, it needs more, of course. |
| 19:58 | <Domenic> | but if you implement a browser in which e.g. console.log doesn't exist or console.assert fails to throw, you risk sites not working. |
| 19:59 | <terinjokes> | yeah, i think the unit tests right now just see if console.* exist and are callable |
| 19:59 | <Domenic> | yeah the tests are nice |
| 20:00 | <terinjokes> | is it in scope that the formatters are script observable in some place |
| 20:00 | <terinjokes> | if #4 is resolved, then it could be done there |
| 20:00 | <terinjokes> | (set the assert message with format specifiers and observe the error message) |
| 20:01 | <Domenic> | interesting |
| 20:02 | <Domenic> | need to build browser interest there i guess |
| 21:42 | <TabAtkins> | Hehe, I love when people forget to actually take something offlist when they say they are. Luckily rubys didn't say anything embarrassing. |