| 07:23 | <annevk> | I was thinking of applying to Outreachy again via Mozilla for someone to work on WHATWG standards, but I'm having trouble coming up with suitable projects. Anyone here with good ideas? |
| 08:48 | <MikeSmith> | annevk: project to look at test coverage for HTML? |
| 08:54 | <annevk> | MikeSmith: I think that's too broad for someone new to all things |
| 09:07 | <MikeSmith> | annevk: something more approachable would be looking at MDN coverage of HTML |
| 09:08 | <MikeSmith> | using the MDN-annotated version of the HTML spec |
| 09:08 | <MikeSmith> | https://arcane-cove-57093.herokuapp.com/multipage/ |
| 09:08 | <MikeSmith> | though there work there would be work on adding content to MDN rather than to the HTML spec |
| 09:09 | <MikeSmith> | could look at places in the spec where there are not MDN annotations yet but where it seems like there should be |
| 09:10 | <annevk> | That's an interesting URL |
| 09:10 | <MikeSmith> | in some cases the fix might just be that there’s already a corresponding MDN article but the article just doesn’t yet have a link back to the HTML spec |
| 09:11 | <MikeSmith> | that URL is the kind of URL heroku creates if you don’t give it an explicit name when you create a heroku app |
| 09:11 | <MikeSmith> | other ones are like cryptic-headland-94862, frozen-bastion-22010 etc |
| 09:14 | <annevk> | This does seem like a useful project, but I'm not sure if I'm the right mentor for it |
| 09:14 | <MikeSmith> | sheppy could be |
| 09:14 | <MikeSmith> | or Chris Mills |
| 09:14 | <MikeSmith> | I guess I could suggest it to them |
| 09:15 | <MikeSmith> | but anyway in general I think for onboarding people to spec-related work, helping them start writing/updating MDN content could be a really good way |
| 09:19 | <MikeSmith> | in other news, thanks to Yves the CSS checker now has up-to-date support for CSS Align3 |
| 09:19 | <MikeSmith> | https://github.com/w3c/css-validator/pull/205 |
| 09:20 | <MikeSmith> | I think the only remaining big gap the CSS checker has as far as conforming to current CSS specs is lack of support for CSS variables |
| 09:21 | <annevk> | \o/ |
| 14:10 | <devsnek> | Domenic: https://github.com/whatwg/streams/pull/950#issuecomment-416961538 |
| 14:11 | <devsnek> | why would we want to implicitly acquire a reader |
| 14:26 | <Domenic> | devsnek: well it just seems like unnecessary ceremony for no gain to make the consumer do it |
| 14:27 | <devsnek> | weird api/10 |
| 14:27 | <TimothyGu> | I feel like it was the right level of layering to do that on the reader level |
| 14:27 | <TimothyGu> | Plus, doing that would allow us to add a separate specialized async iterator for BYOB readers |
| 14:27 | <devsnek> | I posted a thing for what asyncIterator on readablestream might look like |
| 14:28 | <devsnek> | but tim is right we have to add byob with this thing |
| 14:28 | <TimothyGu> | devsnek: the thing you posted LGTM |
| 14:29 | <TimothyGu> | BTW writing a long comment for whatwg streams in node.js rn |
| 14:29 | <devsnek> | hype |
| 14:29 | <devsnek> | I'm not even looking at it anymore lol |
| 14:30 | <TimothyGu> | I can understand why |
| 14:56 | <MikeSmith> | chrisdav_: sheppy FYI https://freenode.logbot.info/whatwg/20180829#c1682181 conversation between annevk and I about Outreachy project idea for work related to MDN coverage for HTML spec |
| 14:56 | <MikeSmith> | oofs |
| 14:56 | MikeSmith | meant that for #mdn on mozilla IRC |
| 15:36 | <TimothyGu> | devsnek: Domenic: https://github.com/nodejs/node/pull/22352#issuecomment-416998268 if either of you wanna 👍 |
| 15:37 | <devsnek> | this isn't a comment its a book |
| 15:37 | <TimothyGu> | ur right |
| 15:37 | <devsnek> | lol popularity charts |
| 15:37 | <devsnek> | timothy i love you |
| 15:41 | <TimothyGu> | lol |
| 15:41 | <TimothyGu> | yes I'll marry you |
| 18:05 | <zcorpan> | TabAtkins: the <wpt> default style... can it be changed to be less obtrusive boxes in the page margin? |
| 18:05 | <TabAtkins> | Come up with an alternate styling and I'm happy to figure something out. Worst case, you can disable Bikeshed's CSS for it and supply your own. |
| 18:06 | <TabAtkins> | (In general tho, I can't count on a page margin to exist, so that's a bit problematic.) |
| 18:06 | <zcorpan> | TabAtkins: I'm thinking about this in the context of HTML |
| 18:30 | <Domenic> | In HTML we should probably use style similar to the caniuse/in-progress MDN links? |
| 18:38 | <MikeSmith> | so the width of the caniuse.com annotations is 9em/144px |
| 18:38 | <MikeSmith> | but some of the WPT filenames are quite long |
| 18:38 | <MikeSmith> | especially, some of the *.serviceworker.* ones |
| 18:43 | <MikeSmith> | so I think for the margin case rather than using a 3-column grid as it has now, it would need to <dt><dd> list thing |
| 18:44 | <MikeSmith> | where the <dt> is the test filename, and the <dd> is (live test) (source) parts, indented |
| 19:19 | <Domenic> | It may also be worth trimming extensions |
| 19:19 | <Domenic> | Although I guess then you could have multiple of the same basename |