| 04:39 | <gsnedders> | Do any drafts of CSS 1 survive any more? |
| 04:40 | <tantek> | like w3.org/tr/css1 with the big red warning |
| 04:46 | <gsnedders> | tantek: nah, I mean actual drafts of it prior to REC |
| 04:46 | <gsnedders> | I found <http://www.w3.org/TR/WD-css1-960220.html>;, but I can't find any index of them |
| 04:47 | <tantek> | you mean before http://www.w3.org/TR/REC-CSS1-961217 ? |
| 04:47 | <gsnedders> | Yeah. |
| 04:48 | <tantek> | that's before my time there unfortunately - not sure where to find those |
| 04:50 | <gsnedders> | really half of what I want is likely in MO space, inc. the archives |
| 07:30 | <zcorpan> | has anyone written a webhook to send an email when a github issue or PR is opened/closed? |
| 07:32 | <gsnedders> | zcorpan: to a given mailing list or what? |
| 07:32 | <zcorpan> | yeah |
| 07:32 | <zcorpan> | public-texttracks for webvtt |
| 07:41 | <gsnedders> | https://help.github.com/articles/receiving-email-notifications-for-pushes-to-a-repository/ may or may not help |
| 07:51 | <zcorpan> | there's email sent to www-dom for whatwg/dom PRs, but it seems that's not a github webhook |
| 08:17 | <zcorpan> | https://github.com/github/github-services/pull/284 -_- |
| 08:27 | <annevk> | zcorpan: it used to be |
| 08:27 | <annevk> | zcorpan: but I removed it |
| 08:28 | <annevk> | zcorpan: talk to dom |
| 08:28 | <zcorpan> | annevk: ok, thx |
| 08:58 | <MikeSmith> | yeah Dom wrote something |
| 10:14 | <pyfisch> | are the encodings for MIME types described in https://tools.ietf.org/html/rfc2231 actually used by browsers? |
| 11:30 | <annevk> | pyfisch: to some extent |
| 11:31 | <annevk> | pyfisch: actually, unsure since that doesn't really define MIME types |
| 12:13 | <pyfisch> | annevk: what encodings of parameters are actually supported by the browser? |
| 12:17 | <annevk> | pyfisch: I'm not sure, I think some might be supported for content-disposition, but I don't really have much knowledge on this |
| 12:34 | <zoey> | Hi, I'm new and I would like to contribute, can someone get me started? This is in reference to Outreachy. |
| 12:36 | <Ms2ger> | Welcome zoey |
| 12:36 | <annevk> | zoey: did you read through https://wiki.mozilla.org/Outreachy/2016/December_to_March? |
| 12:37 | <annevk> | zoey: in particular, the bit about HTML |
| 12:38 | <zoey> | Yes, I have read the bit about HTML. I have knowledge of HTML and CSS. |
| 12:39 | <annevk> | zoey: alright, any of the bugs/issues look interesting? |
| 12:40 | <annevk> | zoey: e.g., you could attempt to fix https://www.w3.org/Bugs/Public/show_bug.cgi?id=28076 which is just a simple grammar issue |
| 12:40 | <annevk> | well, wording |
| 12:40 | <zoey> | Okay |
| 12:43 | <annevk> | zoey: for what it's worth, I'm at a conference this week so might always be available on IRC, but feel free to email and I'll try to reply as soon as possible |
| 12:44 | <annevk> | zoey: hopefully that's not too inconvenient |
| 12:45 | <zoey> | Its fine, I'm new to this so I'll probably take some time to figure things out. |
| 12:48 | <annevk> | zoey: thank you for trying it out and there will usually be someone here who can help you get unstuck (may you get stuck in the first place) |
| 13:19 | <zoey> | I found out that on line 648 colspan="2" but there is only one column defined! So there would be an error! |
| 17:02 | <IZh> | Hi. What you think about the post about <input>: http://meowni.ca/posts/a-story-about-input/ ? |
| 17:40 | <zoey> | So should I just keep debugging some HTML code? |
| 17:57 | <caitp> | what have you been doing so far? I saw you got linked an editorial bug earlier |
| 20:19 | <johnme> | annevk: is https://github.com/whatwg/notifications/pull/48 ready to land? |
| 21:46 | <Joseph_Silber> | Why can't a label's for attribute refer to an input's name? |
| 21:46 | <Joseph_Silber> | Why do I have to pollute everything with IDs? |
| 21:54 | <svl> | Joseph_Silber: multiple input elements can share the same name. Only ID attributes 'require' uniqueness. |
| 21:55 | <Joseph_Silber> | So it should have some some algorithm to determine it. Probably the first one. |
| 21:56 | <Joseph_Silber> | The first one in the current form. |
| 21:56 | <Joseph_Silber> | It's quite common to have multiple forms on the same page. Imagine they both collect an email. They would both have an input named `email`. |
| 21:57 | <Joseph_Silber> | Using a label `for="email"` is quite intuitive. |
| 21:57 | <Joseph_Silber> | Instead, I have to now give them separate email_1 and email_2 IDs. |
| 21:57 | <Joseph_Silber> | Ugh! |
| 21:58 | <Joseph_Silber> | <svl> multiple input elements can share the same name. Only ID attributes 'require' uniqueness. |
| 21:58 | <Joseph_Silber> | Good thing you put require in scare quotes, because it's not enforced anywhere. |
| 21:58 | <Joseph_Silber> | Your CSS will still work. |
| 21:58 | <Joseph_Silber> | Even querySelectorAll('#non-unique-id') will select them all. |
| 21:59 | <Joseph_Silber> | Only getElementById('non-unique-id') will return the first one. |
| 21:59 | <Joseph_Silber> | Not that I would EVER advise anyone to have non unique IDs. |
| 22:00 | <Joseph_Silber> | Regardless, I don't see how allowing `for` to match against `name` is a bad idea. |
| 22:02 | <nox> | It seems like https://html.spec.whatwg.org/multipage/comms.html#dom-websocket-bufferedamount doesn't match Blob.size, |
| 22:02 | <nox> | yet WebSocket.send() can take a Blob argument, and must increase bufferedAmount by that Blob's size. |