| 01:28 | <Domenic> | Oh wow, the Web IDL XSLT toolchain lives on in web crypto: https://github.com/w3c/webcrypto/tree/master/spec |
| 01:28 | <Domenic> | who knew |
| 04:18 | <MikeSmith> | Domenic: XSLT the selfish gene |
| 04:50 | <GPHemsley> | Are people still having trouble with the wiki? |
| 04:52 | <GPHemsley> | wiki.whatwg.org seems to be timing out for me |
| 04:52 | <GPHemsley> | for both https and sftp |
| 04:52 | <GPHemsley> | but not for ping |
| 04:52 | <GPHemsley> | oh wait |
| 04:53 | <GPHemsley> | there it goes |
| 04:53 | <GPHemsley> | sftp is still timing out |
| 05:00 | <GPHemsley> | annevk: Can you check in the site configuration to ensure sftp is still turned on correctly? |
| 05:03 | <GPHemsley> | and/or ssh |
| 05:21 | <MikeSmith> | GPHemsley: the wiki has been working fine for me recently |
| 05:21 | <MikeSmith> | but that said the only thing I have been doing it to set up redirect to content elsewhere |
| 05:22 | <MikeSmith> | because at least for content I care about myself I’m not going to be relying on it any longer |
| 05:23 | <MikeSmith> | between that weird wiki database error and the Dreamhost IPv6 brokenness for whatwg.org it’s not usable for what I need it for |
| 05:24 | <MikeSmith> | which is to say, mostly for the HTML checker |
| 05:26 | <MikeSmith> | I had the HTML checker build set up to grab content (e.g., the MicrosyntaxDescriptions page) from the wiki at build time, and if that failed the build fails, basically |
| 06:10 | <GPHemsley> | hmm |
| 06:11 | <GPHemsley> | well someone ping me if the database error appears again |
| 06:11 | <GPHemsley> | I do eventually read my pings |
| 06:12 | <GPHemsley> | I haven't actually seen the error myself |
| 06:14 | <GPHemsley> | direct e-mail for anything urgent |
| 06:14 | <GPHemsley> | @gmail |
| 06:54 | <MikeSmith> | GPHemsley: ok, thanks |
| 08:28 | <annevk> | GPHemsley: I forwarded the request |
| 08:48 | <annevk> | GPHemsley: thanks for taking a look, btw |
| 12:55 | <annevk> | Domenic: https://github.com/w3c/IndexedDB/issues/87 is of interest to you I think |
| 14:30 | <annevk> | MikeSmith: does GitHub provide some kind of feature for overlong wpt-stability-bot comments to be clipped by default? |
| 14:30 | <annevk> | MikeSmith: https://github.com/w3c/web-platform-tests/pull/4104#issuecomment-269637001 is somewhat bad, especially as you try to find the next useful comment |
| 14:36 | <gsnedders> | annevk: <details>, but then you hit the cross-browser styling issues |
| 14:36 | <gsnedders> | annevk: and you don't control the stylesheet, obviously |
| 14:37 | <annevk> | gsnedders: oh, if that works that seems alright, only when there's so many words in the comment I guess |
| 14:40 | <gsnedders> | oh, they seem to have fixed it, so the <details> element triangle now does appear in Firefox |
| 14:41 | <gsnedders> | so yeah, that works now |
| 14:59 | <MikeSmith> | annevk: what gsnedders said |
| 14:59 | <MikeSmith> | if github fixed their <details> but then we should update the stability checker to do use it |
| 15:00 | <MikeSmith> | gsnedders: you wanna file an issue for that or you want me to? |
| 15:01 | <MikeSmith> | I thought jgraham had implemented <details> output for it but then had to be back it out because of that github bug |
| 15:01 | <MikeSmith> | but maybe I just dreamed that |
| 15:14 | <gsnedders> | MikeSmith: you do |
| 15:16 | gsnedders | heads out |
| 17:43 | <annevk> | GPHemsley: should all still work |
| 17:43 | <annevk> | GPHemsley: did you lose credentials? Or just timing out? Both sftp and ssh? |
| 17:56 | <MikeSmith> | annevk: take a look at https://github.com/w3c/web-platform-tests/pull/4407 please |
| 17:58 | <jgraham> | MikeSmith, gsnedders: <details> doesn't work anyway because you can't use markdown inside the element |
| 17:58 | <jgraham> | Which you want for the table or the text logs become unreadable |
| 17:58 | <jgraham> | and most people have to use the text logs |
| 17:59 | <MikeSmith> | jgraham: seems like you can use markdown inside details actually |
| 17:59 | <MikeSmith> | look at the comments in https://github.com/w3c/web-platform-tests/pull/4407 |
| 17:59 | <jgraham> | Oh? When I tried this a couple of weeks ago you couldn't for sure |
| 17:59 | <MikeSmith> | yah |
| 17:59 | <MikeSmith> | I think they maybe fixed that at the same time the first the disclosure-triangle bug |
| 17:59 | <jgraham> | Fair enough |
| 18:01 | MikeSmith | goes back to his MDN editing marathon for now |
| 18:02 | <jgraham> | MikeSmith: r+ please merge whenever |
| 18:09 | <MikeSmith> | jgraham: w00t |
| 18:09 | <MikeSmith> | thanks |
| 18:20 | <MikeSmith> | annevk: rebase your PRs |
| 18:21 | MikeSmith | now heads off to sleep |
| 19:22 | <Domenic> | Makign specs work offline https://github.com/whatwg/streams/pull/637 |
| 22:39 | <Domenic> | annevk: hmm why do some of your specs omit the index and idl-index? |
| 22:52 | <zcorpan> | https://html.spec.whatwg.org/#parsing-main-inbody:special-3 .... am I missing something or does the spec not have a parse error for <!doctype html><body></adsfasdf> ? |
| 22:53 | <zcorpan> | it seems to me it's only a parse error if asdfasdf is on the stack (and not the current node after implied end tags), or is in the special category |
| 22:54 | <gsnedders> | zcorpan: also surely the algorithm doesn't terminate in that case?! |
| 22:54 | <gsnedders> | i.e., you'll just keep "Set node to the previous entry in the stack of open elements." |
| 22:55 | <zcorpan> | ah yeah. :-| |
| 22:55 | <zcorpan> | weird!? |
| 22:55 | gsnedders | starts seeing value in what he decided not to do earlier in the year again with formally verifying parts of the parser again… |