06:54
<annevk>
GitHub changed fonts?
07:01
<ondras>
yes
07:01
<ondras>
about a week ago
07:42
<nox>
annevk: System fonts now.
08:15
<smaug____>
does anyone know why https://html.spec.whatwg.org/multipage/browsers.html#navigate javascript: part special cases document's address?
08:15
<smaug____>
very surprising
08:20
<annevk>
smaug____: I guess that's what browsers do?
08:20
<smaug____>
some do
08:20
<smaug____>
some don't
08:21
<smaug____>
how does one get sane text editing in github issues
12:43
<Guest79275>
annevk: not sure what you mean by the URL fetching pinning blob being defined
12:43
<Guest79275>
and that it clones the blob
12:43
<annevk>
Well, the URL parser clones the Blob object and stores it on the returned URL, right?
13:00
<annevk>
Is GitHub really slow?
17:52
<Domenic>
smaug____: to put in code or other things with special characters, surround it with backticks: `<script>`
17:53
<TabAtkins>
nox: Theoretically, sure. At the moment it only supports generating single-page things, so you wouldn't be able to put together a full epub structure, but it wouldn't be too hard to enable that probably.
17:54
<TabAtkins>
(I have an echidna-publish option that puts together TAR files of the spec and all supporting files, so doing a multi-file thing that way is easy.)
18:40
<smaug____>
Domenic: ah, right. I tend to try always ยด or ', because Finnish keyboard has those keys and ` is behind some modifier
18:42
<TabAtkins>
Markdown's special character set is clearly designed around American keyboards, yeah.
20:53
<smaug____>
aha, 'run synthetic click activation steps ' is buggy. I'm pretty sure it should use 'nearest activatable element'
20:53
<smaug____>
and 'nearest activatable element ' doesn't seem to quite work with <button>'s which aren't in any form
21:09
<smaug____>
filed https://github.com/whatwg/html/issues/1567