| 09:12 | <Ms2ger> | JavaScript error: http://www.whatwg.org/specs/web-apps/current-work/updater.js, line 71: configUI is null |
| 09:12 | <Ms2ger> | JavaScript error: http://www.whatwg.org/specs/web-apps/current-work/status.js, line 1155: configUI is null |
| 10:36 | <Ms2ger> | Wow |
| 10:36 | <Ms2ger> | SVG2 points at http://www.w3.org/TR/Window/#embeddingelt |
| 10:41 | <jgraham> | :-o |
| 16:09 | <annevk> | I wish there was an @antimattursource account |
| 16:11 | <Ms2ger> | Nice explanation of script/async/defer: http://peter.sh/experiments/asynchronous-and-deferred-javascript-execution-explained/ |
| 16:11 | <annevk> | http://about.monash/#tlds lol |
| 16:11 | <annevk> | Ms2ger: yeah, filed a bug on HTML to include it just now |
| 16:11 | Ms2ger | approves |
| 16:11 | <Ms2ger> | Btw |
| 16:11 | <annevk> | Ms2ger: provided beverloo_ approves |
| 16:12 | <Ms2ger> | It seems like data url parsing still needs work? |
| 16:12 | <annevk> | Ms2ger: you think? |
| 16:12 | <annevk> | ;-) |
| 16:13 | <annevk> | First thing tomorrow is data URL security boundaries |
| 16:13 | <Ms2ger> | Mm |
| 16:13 | <Ms2ger> | Rather you than me :) |
| 16:13 | <annevk> | Need to get the exchange with sicking into specifications and Gecko |
| 16:14 | <annevk> | As for data URL parsing, I still have hopes someone else will pick that up |
| 16:15 | <Ms2ger> | There's http://simonsapin.github.io/data-urls/ |
| 16:15 | Ms2ger | would like to have another 24 hours a day for spec work |
| 17:13 | <SimonSapin> | "For users, it will mean greater security, a better user experience, more useful searches, and improved navigation." New TLDs are magical, it seems. |
| 17:35 | <Hixie> | does html5lib support <template>? and if so, does it do anything special with its contents, or does it just put the template contents as children of the <template> itself? |
| 17:40 | <Ms2ger> | I'd be somewhat surprised |
| 18:55 | <jgraham> | Hixie: Not unless gsnedders landed something I forgot about |
| 20:26 | <zewt> | ... why do people keep using "```js" forum/tracker markup on mailing lists all of a sudden? are people posting from a broken forum/list gateway or something? heh |
| 20:29 | <caitp-> | because we know that you're probably familiar with gfm and understand how you're supposed to understand it |
| 20:30 | <zewt> | it's markup, you don't write markup with humans as the audience (and we all know how to interpret javascript in an email) |
| 20:31 | <caitp-> | inboxapp.co might prettify gfm codeblocks in emails on its own some day |
| 20:32 | <zewt> | i'd sure hope not, it'd break "email interop" with the rest of the universe |
| 20:32 | <caitp-> | email interop has already broken |
| 20:33 | <zewt> | "the system isn't perfect, therefore it's okay to do anything" no |
| 20:34 | <caitp-> | nobody is working to improve email really, there aren't very many competing email clients, so people can pretty much do whatever they want with it |
| 20:40 | <zewt> | "can" and "should" are very different things |
| 20:43 | <caitp> | i'm sure the folks reading email on their 5250 terminals might be less happy about it, but for people who aren't living in the 70s it's great |
| 20:43 | <caitp> | nice readable code, beautiful |
| 20:44 | <zewt> | ... |
| 20:44 | <zewt> | itym 'folks using an email client that isn't "inboxapp.co"' |
| 20:44 | <caitp> | i'm sure there's a chrome extension to make gmail render gfm, and if there isn't it would be trivial to write |
| 20:45 | <zewt> | uhh |
| 20:45 | <caitp> | or a thunderbird plugin |
| 20:45 | <zewt> | writing emails with the expectation that everyone else is going to install a browser plugin for them to be formatted correctly would be pretty absurd |
| 20:46 | <caitp> | even without browser plugins, it's still designating that a block of text is code, and designating the language the code is in |
| 20:46 | <caitp> | so I think it's still pretty easy to reason about |
| 20:52 | <SamB> | as long as it looks okay in gnus out-of-the-box |
| 20:56 | jgraham | wonders what gfm is |
| 20:56 | <caitp> | github's extensions to markdown |
| 20:57 | <caitp> | the f is for "flavoured" |
| 20:57 | <caitp> | the g and m should be self explanatory |
| 20:59 | <jgraham> | Oh right. Their random additions to a poorly-specified markup format. I'm not sure that I would want that as the basis for anything. |
| 20:59 | <caitp> | hey, you could always form a w3c community working group for it ;) |
| 21:00 | <caitp> | for all that would accomplish --- realistically, it's there, and it's ubiquitous, so people use it |
| 21:00 | <jgraham> | It's pretty absurd that you are calling it "ubiquitous" just after you had to explain to me what it was |
| 21:00 | <caitp> | ubiquity doesn't mean everyone has heard of it |
| 21:01 | <caitp> | but it's used heavily on the most popular public and private repository host, and has found its way into mailing lists, jira, and bugzilla too |
| 21:01 | <caitp> | so, it's all over the place |
| 21:05 | <jgraham> | I can't see any evidence that bugzilla or Jira have GitHub extensions to markdown. |
| 21:07 | <caitp> | I know bugzilla won't render GFM, but GFM is used on bugzilla now and again |
| 21:07 | <caitp> | atlassian products support variations on it |
| 21:07 | <caitp> | etc |
| 21:10 | <jgraham> | That seems like a substantially different claim |
| 22:00 | <zewt> | (i certainly don't know what it is, i just assumed "something something markup") |
| 22:01 | <zewt> | (gfm are my initials, but that seemed improbable) |
| 22:21 | <gsnedders> | Hixie: no, we don't support template. plan was just to put stuff as the children of the template itself |
| 22:51 | <Hixie> | gsnedders: k. i guess i'll do the same in my library. |
| 22:53 | <SamB> | jgraham: I guess you don't like patched versions of org-mode either ;-P |