12:02
<tobie>
annevk: what does the "w(...)" stand for here: https://github.com/heycam/webidl/pull/517#issuecomment-361855121
12:10
<Domenic>
tobie: it stands for "console.log"; it's the syntax used in http://software.hixie.ch/utilities/js/live-dom-viewer/
12:11
<Domenic>
Hmm so am I reading right that plans to use rust-url in Gecko have been abandoned? /cc nox
12:23
<tobie>
Domenic: ty
12:51
<nox>
Domenic: Didn’t hear about that.
12:52
<Domenic>
nox: https://bugzilla.mozilla.org/show_bug.cgi?id=url-oxidation
12:53
<nox>
There is still MozURL.
16:55
<Domenic>
How did Bikeshed figure out that it was safe to turn my ' into a ’ inside a code example? It was safe because it was inside a JS comment... is it really that smart?
16:55
<Domenic>
Not complaining, just impressed/confused
17:24
<railgun>
Domenic: apologies for taking the question seriously, but here are the revelant bits (I want to contribute to Bikeshed as well so this was a fun exercise for me)
17:24
<railgun>
fixTypography: https://i.imgur.com/Gf3hSrh.jpg gets called in fixText here: https://i.imgur.com/lLVIxSl.jpg
17:27
<railgun>
not sure where to go from here though (does the regex handle it or something in fixText?)
17:35
<railgun>
unrelated, but is there a reason why pages like https://html.spec.whatwg.org/dev/sections.html#the-nav-element don't have syntax highlighting?
17:44
<Domenic>
Yeah, HTML uses a different build toolchain :-/. MikeSmith has a patch ready to add syntax highlighting but I think it's waiting on some integration work from TabAtkins?
17:44
<TabAtkins>
Argh, yes, it's waiting on me. :(
17:47
<railgun>
oh hey TabAtkins thanks for creating Bikeshed!
17:48
<TabAtkins>
Domenic: Re smartquote, no, it's not actually that smart. But it does avoid doing the fix on word-ending apostrophes, so it won't catch programming-related quote usage accidentally.
17:49
<Domenic>
hmm i see
17:49
<TabAtkins>
railgun: Welcome. ^_^ I did it for myself, and just got lucky that so many other people needed a better toolchain for this stuff too. ^_^
17:49
<Domenic>
So it's not safe from a hypothetical language that has some literal syntax like 'foo'u8 or similar
17:49
<TabAtkins>
Domenic: It's super dumb https://github.com/tabatkins/bikeshed/blob/master/bikeshed/htmlhelpers.py#L596
17:49
<TabAtkins>
yeah
17:51
<TabAtkins>
I'm not sure why I'm doing this over the text before parsing it, tho. All of these transforms would work just fine over the post-parsing text, and then I could avoid code/pre (or be super smart and run it in comments, tho I guess that's still potentially fraught).
18:04
<railgun>
TabAtkins: that explains why I couldn't find anything relevant haha
18:04
<railgun>
yeah I noticed the section where you undo fixTypography iirc
18:05
<TabAtkins>
That whole thing is some bad remnants of my original, much hackier code. Should rip it out and do it proper at some point.
18:12
<railgun>
Domenic: sorry I missed the syntax highlighting bit, that's great
23:05
<ska>
Can I point fetch() to a local file?
23:06
<ska>
If so, how?
23:13
<Mek>
no, you can't fetch from a local file
23:52
<railgun>
is it fine if I just open the source file in my browser to preview the changes I make locally?
23:52
<railgun>
or is there a better way to do it
23:55
<TimothyGu>
railgun: for bikeshed? I build the output first before previewing :p
23:56
<ska>
FOr some reason, when I download the file and put it up on my localweb, fetch() is unable to get it.
23:56
<ska>
Is there some meta-magic I need to provide?
23:57
<railgun>
TimothyGu: right now I'm just opening the whatwg/html source file in my browser
23:57
<TimothyGu>
railgun: oh for whatwg/html
23:57
<railgun>
yeah
23:58
<TimothyGu>
hmm I don't think I've ever previewed
23:58
<TimothyGu>
I guess if opening the source file works, great
23:58
<TimothyGu>
you do know how to create the spec from the source files right
23:59
<railgun>
most of it works, just some colors and links don't work
23:59
<TimothyGu>
through whatwg/html-build
23:59
<TimothyGu>
https://github.com/whatwg/html-build