| 03:02 | <wanderview> | Domenic: I don't think I'm going to get to writing that systems benchmark for async read any time soon |
| 03:06 | <wanderview> | too many Cache fires to put out |
| 03:32 | <annevk_> | TabAtkins: awesome, will review later |
| 03:39 | <wanderview> | annevk: you must be up with a baby? |
| 03:46 | <annevk> | wanderview: hehe |
| 03:46 | <annevk> | wanderview: he is a bit sick |
| 03:46 | <wanderview> | ouch :-( |
| 03:46 | <wanderview> | thats no fun |
| 03:46 | <annevk> | wanderview: but also I'm suffering from some sleeping trouble this week |
| 03:46 | <wanderview> | ah... thats no fun either |
| 03:47 | <annevk> | wanderview: it's more me than him I think :-) he holds it together pretty well |
| 03:47 | <wanderview> | annevk: I've had this thing lately where I can sleep from 9pm to 10pm... then wake up until midnight |
| 03:47 | <annevk> | wanderview: anyway, after I took care of him I decided to take a bath and then got a bunch of ideas for work so I decided to write them down |
| 03:48 | <annevk> | ugh |
| 03:48 | <wanderview> | awesome... new storage features based on dreams! |
| 03:49 | <wanderview> | :-) |
| 03:49 | <wanderview> | and... my daughter just woke up |
| 03:49 | <annevk> | "dream" boxes are fairly magical |
| 03:59 | <wanderview> | ok... finally done with this cache mess for the night... g'night |
| 05:40 | <Domenic> | annevk: would you be interested in my streams build system that generates commit snapshots, allows you to avoid committing generated output to the repo, and runs bikeshed on a CI server to ensure you always get the latest code? |
| 05:40 | <annevk> | Domenic: possibly if you are up for maintaining it |
| 05:41 | <annevk> | Domenic: trying to fix the DOM header at the moment |
| 05:41 | <Domenic> | annevk: yeah I've been planning to generalize/document it for a while, if I have a customer lined up that'll be extra incentive |
| 05:41 | <annevk> | Domenic: both DOM and URL could make use of it |
| 05:41 | <Domenic> | annevk: https://github.com/whatwg/streams/blob/master/index.bs#L15-L19 may help |
| 05:41 | <annevk> | Domenic: hopefully more down the line |
| 05:41 | <Domenic> | Notifications too IIRC |
| 05:41 | <annevk> | Domenic: yes |
| 05:42 | <annevk> | thanks to Peter |
| 05:42 | <annevk> | Domenic: with Fetch I opted to first link to the repo and then have (new issue, open issues) following it |
| 05:43 | <Domenic> | Hmm that is kind of nice |
| 05:45 | <Domenic> | why does Firefox randomly decide it likes svg favicons... ~1/20 tabs I open to a WHATWG spec have a nice favicon, seemingly at random. |
| 05:45 | <Domenic> | Huh there's a whole caniuse for this http://caniuse.com/#feat=link-icon-svg |
| 05:45 | <Domenic> | Well I guess that explains it https://bugzilla.mozilla.org/show_bug.cgi?id=366324#c14 |
| 05:46 | <annevk> | Domenic: do you know why I have to include "URL: https://dom.spec.whatwg.org"; to get relative links to DOM definitions? |
| 05:46 | <annevk> | Domenic: including that also generates a "This version" field which is pointless |
| 05:46 | <annevk> | Domenic: you don't seem to have that at all |
| 05:47 | <Domenic> | Yeah was just checking... hmm |
| 05:47 | <Domenic> | I don't use {{ microsyntaxes though just <a>term</a>, maybe that's the difference? |
| 05:47 | <annevk> | TabAtkins: you awake? |
| 05:49 | <TabAtkins> | annevk: What's up? |
| 05:49 | <annevk> | TabAtkins: various things it seems |
| 05:49 | <annevk> | TabAtkins: why do I need to include URL: ...? I don't want "This version" but I also want relative links |
| 05:50 | <annevk> | TabAtkins: Domenic filed various issues on things that are wrongish, e.g. https://github.com/whatwg/dom/issues/22 |
| 05:50 | <Domenic> | https://github.com/whatwg/dom/issues is mostly me at this point |
| 05:51 | <TabAtkins> | Ooh, I wonder if I'm skipping over <code> elements for autolink processing? |
| 05:53 | <TabAtkins> | I guess you don't need URL; looks like Streams doesn't have it. |
| 05:53 | <MikeSmith> | annevk: https://lists.w3.org/Archives/Public/www-tag/2015Apr/0027.html seems like nice progress |
| 05:53 | <annevk> | TabAtkins: if I remove it all fragment-only links get that URL prepended |
| 05:53 | <annevk> | MikeSmith: yeah |
| 05:54 | <annevk> | MikeSmith: I wonder what happened |
| 05:54 | <MikeSmith> | they got smarter? |
| 05:54 | <MikeSmith> | they got smarter people in to work on it? |
| 05:54 | <TabAtkins> | annevk: URL metadata definitely has zero effect on links, so I dunno what you think is going on. Gimme a specific element that's being weird, so I can check it out? |
| 05:55 | <annevk> | MikeSmith: if I'd be cynical I'd say it's too thwart the competition |
| 05:55 | <annevk> | TabAtkins: hmm maybe it was another field I changed |
| 05:56 | <MikeSmith> | annevk: maybe you're right https://twitter.com/dakami/status/588548153504239616 |
| 05:56 | <annevk> | TabAtkins: does Shortname have an effect? |
| 05:56 | <annevk> | to* |
| 05:56 | <Domenic> | I too find the existence of shortname confusing |
| 05:56 | <TabAtkins> | Yes it does; gimme a sec. |
| 05:57 | <MikeSmith> | https://people.freebsd.org/~rrs/asiabsd_2015_tls.pdf seems like it has some pretty interesting details about their deployment/implementation |
| 05:57 | <Domenic> | Oh nice file-issue.js just worked :D |
| 05:58 | <annevk> | Domenic: yeah also did for Notifications, very nice |
| 05:59 | <TabAtkins> | At minimum, Shortname lets Bikeshed know what definitions in the linking database are for the current spec, so it should ignore them (rather than treating them as ambiguous link targets). |
| 05:59 | <TabAtkins> | If you did multiple levels, Shortname+Level helps with that in a similar way. |
| 06:00 | <Domenic> | So shortname is an index into the bikeshed linking database? |
| 06:01 | <TabAtkins> | It's one of the things that identifies an anchor, yeah. |
| 06:01 | <TabAtkins> | When you set a Link Defaults, it's the shortname that you're specifying. |
| 06:02 | <Domenic> | then i guess my question is who's squatting on "dom" and forcing "dom-core-ls" on us :P |
| 06:04 | <annevk> | TabAtkins: two issues left https://github.com/whatwg/dom/issues and I guess the question who's squatting "dom" :-) |
| 06:04 | <TabAtkins> | Looks like nobody - I don't see "dom" in the linking database. |
| 06:06 | <TabAtkins> | I'll just need to change it in Shepherd to track the alteration. Want me to do so? |
| 06:06 | <TabAtkins> | (The -ls is the level part; the shortname is dom-core.) |
| 06:10 | <annevk> | TabAtkins: so it would be dom-ls? |
| 06:10 | <annevk> | TabAtkins: might be nice to just get it over with now |
| 06:17 | <TabAtkins> | k, done |
| 06:17 | <TabAtkins> | Shortname is now "dom". |
| 06:18 | <TabAtkins> | Full levelled name is "dom-ls". |
| 06:19 | <TabAtkins> | Oh, and looks like the reason your shortname was set to dom-core is because that was the name of your index file - dom-core.html. |
| 06:26 | <annevk> | TabAtkins: looks like https://dom.spec.whatwg.org/#htmlcollection is missing some links too |
| 06:26 | <annevk> | TabAtkins: and dfn.js appears broken |
| 06:27 | <TabAtkins> | What links do you think it's missing? (Besides the {{}} stuff showing up.) |
| 06:30 | <annevk> | TabAtkins: item and namedItem are not clickable |
| 06:31 | <annevk> | TabAtkins: and index and name are marked bold while they're really variables |
| 06:31 | <annevk> | the latter might be a Bikeshed thing |
| 06:31 | <annevk> | (talking about the IDL block) |
| 06:32 | <TabAtkins> | Yeah, I see that item/nameditem aren't properly picking up the definitions later. (They're giving an independent definition, and I'm trying to figure out why.) |
| 06:33 | <TabAtkins> | Arguments are marked up/defined in Bikeshed. If you don't want them styled specially, add a `dfn[data-dfn-type=argument]` style rule. |
| 06:36 | <TabAtkins> | Ah, I see, I have some lingering hackiness from when I was doing IDL worse. Hmmm. |
| 06:46 | <TabAtkins> | Ugh, it's as I thought. I've got a mutually reinforcing set of legacy hacks from back when I wasn't handling IDL correctly, and fixing them properly will be some work. I'll get on that tomorrow. |
| 06:47 | TabAtkins | is pretty sure he'll need some extra data files for efficient querying of function overloads. |
| 06:54 | <annevk> | TabAtkins: thanks, happy we got this far :-) |
| 07:14 | <annevk> | Domenic: if I wanted to fix some things in Streams, should I PR index.bs or just file issues? |
| 07:16 | annevk | will file issues for now |
| 08:50 | <zcorpan> | FATAL ERROR: No 'idl' refs found for 'Document' with spec 'dom-core-ls'. -_- |
| 09:11 | <zcorpan> | hmm seems it's fine when generated on the server |
| 09:12 | <zcorpan> | but i get mail saying to choose between svg2 and html5 for {{Document}} |
| 09:12 | <zcorpan> | TabAtkins: ^ |
| 09:25 | <annevk> | zcorpan: use 'dom' or 'dom-ls' as token |
| 09:26 | <zcorpan> | annevk: that still gives fatal error for `Document`. but maybe this will fix itself since it's generated without warnings on csswg server |
| 09:27 | <zcorpan> | (and it points to the dom spec) |
| 09:39 | <annevk> | zcorpan: TabAtkins did note something about Document not working well |
| 09:39 | <annevk> | zcorpan: maybe file an issue against bikeshed? |
| 09:40 | <zcorpan> | ok |
| 09:40 | <annevk> | zcorpan: hopefully everything WHATWG can be bikeshed by end-of-year (prolly minus HTML) |
| 09:43 | <zcorpan> | https://github.com/tabatkins/bikeshed/issues/387 |
| 13:30 | <mounir_> | Ms2ger: default values for dictionary would allow: dictionary Bar { DOMString[] foo = []; }; ? |
| 13:30 | <Ms2ger> | I don't think so |
| 13:31 | <mounir_> | Ms2ger: no default values for array or sequences? |
| 13:32 | <Ms2ger> | Not that I recall |
| 14:05 | <Ms2ger> | TabAtkins, is FileAPI the awful formatting spec? |
| 14:21 | <annevk> | mounir_: also, DOMString[] is not valid there |
| 14:21 | <annevk> | mounir_: you want sequence |
| 14:21 | <Domenic> | How many specs would we have to update to change X[] to LegacyFakeArrayLike<X>, I wonder. |
| 14:22 | <mounir_> | annevk: readonly sequence<DOMString> in the Event interface too? |
| 14:23 | <annevk> | mounir_: we don't have a good thing for that yet |
| 14:24 | <mounir_> | it sounds good to you to have sequence<> in EventInit and DOMString[] in the Event interface? |
| 14:24 | <mounir_> | annevk: ^ |
| 14:25 | <annevk> | mounir_: no, [] is never good |
| 14:25 | <annevk> | mounir_: see https://www.w3.org/Bugs/Public/show_bug.cgi?id=23682 |
| 14:25 | <annevk> | Domenic: too many |
| 14:49 | <TabAtkins> | Ms2ger: Depends on what you mean by "awful formatting". |
| 14:49 | <Ms2ger> | What you complained about on twitter :) |
| 14:51 | <TabAtkins> | Oh, yeah, it was terrible. |
| 14:51 | <TabAtkins> | Some lists had their <li>s indented four or five different ways, for 9 items. |
| 14:52 | <TabAtkins> | And, like, the ids for sections dont' follow any pattern. The Blob IDs are totally different structure from the File IDs. |
| 14:52 | <TabAtkins> | So much inconsistency laced throughout the entire thing. |
| 14:53 | <TabAtkins> | And don't get me started on the spec starting with a 2-space indent, but of course randomly switching to 3 or 4 space in some places. |
| 14:55 | <caitp> | i'm surprised nobody came up with a clang-formatter for whatever the spec docs are written in |
| 14:56 | <TabAtkins> | I've strongly considered it. |
| 14:56 | <TabAtkins> | But it's a lot of work. ^_^ |
| 14:56 | <caitp> | somewhere out there there's a bored highschool student who'd do it |
| 14:57 | <TabAtkins> | Well, who'd do it halfway. |
| 15:13 | <jgraham> | So which is the most reusable "file a bug on this bit of spec" script these days? |
| 15:15 | <TabAtkins> | Apparently the one DOM/Streams is using just works out of the box pretty good. |
| 15:15 | <Domenic> | jgraham: file-bug.js for W3C bugtrackers, file-issue.js for GitHub |
| 15:15 | <jgraham> | Domenic: From dom/streams? |
| 15:18 | <annevk> | jgraham: it's on resources.whatwg.org |
| 15:18 | <jgraham> | Domenic: Right, got it, thanks |
| 15:18 | <jgraham> | annevk: Thanks also |
| 15:18 | <jgraham> | And also TabAtkins |
| 15:18 | <jgraham> | So much thanks! |
| 15:19 | <annevk> | TabAtkins: yeah that spec was a bit of a disaster |
| 15:19 | <TabAtkins> | annevk: Well Im fixing it, at least. Since it's a much shorter spec, only ~1900 lines, I can do a thorough reformat without killing myself. |
| 15:19 | <TabAtkins> | DOM made me want to die. |
| 15:20 | <annevk> | DOM is pretty big |
| 15:20 | <TabAtkins> | Which is why it took 3 months to finish. ^_^ |
| 15:20 | <TabAtkins> | At least you were *extremely* consistent in link formatting, which made things *way* easier. |
| 15:20 | <TabAtkins> | I often find a given term linked with four different syntaxes in FileAPI. |
| 15:21 | <annevk> | Yeah, I optimize for basic search and replace that doesn't require regular expressions |
| 15:22 | <TabAtkins> | My fingers and sanity thank you for it. |
| 15:22 | <TabAtkins> | And thank jgraham, while I'm at it. |
| 15:23 | <Ms2ger> | ? |
| 15:23 | <flyrock> | TabAtkins, annevk ! I have only read one book on html/css , no experience , that was responsive web design by ben frain. and i wanna be one of you guys, where to start. |
| 15:24 | <TabAtkins> | Ms2ger: Well, he was thanking all of us, so I felt I had to return the favor. |
| 15:24 | <Ms2ger> | Ah, heh |
| 15:25 | <TabAtkins> | flyrock: My path was to learn web dev, subscribe to the standards mailing lists, gradually learn how things worked (and why they worked the way they did), and then finally find a topic I was passionate about and thought I could improve. |
| 15:25 | <TabAtkins> | flyrock: So if you're just starting, you've got a few years of experience-building to go before you should consider trying to work on specs. ^_^ |
| 15:26 | <flyrock> | TabAtkins,i got it, thanks for you time, will keep bugging you occasionally ! |
| 15:27 | <TabAtkins> | np |
| 15:27 | <TabAtkins> | (Of course, the topic I thought I could improve I still did a lot of damage to - yay gradients! But the end-result was indeed much better.) |
| 15:30 | <flyrock> | i suppose that's you being modest. :) |
| 15:30 | <TabAtkins> | No, I really fucked it up and did a lot of damage. It's all healed over now, but dealing with the four different gradient syntaxes that existed at the same time was hellish. |
| 15:31 | <caitp> | you can't accomplish anything without ruining at least one other thing, that's just how it goes |
| 15:31 | <TabAtkins> | When god closes a door, he breaks a window. |
| 15:31 | <flyrock> | TabAtkins, I think i will take some time to decipher what you explained, but we will sure talk about it. |
| 15:33 | <TabAtkins> | flyrock: Just dont' jump ahead of yourself. Spec work is weird meta-work over webdev. You need a strong webdev knowledge base to do it well, and even then most people aren't suited for it, and that's fine. |
| 15:33 | <TabAtkins> | It requires a bizarre mix of patience and impatience that is intensely frustrating to most people. |
| 15:34 | <TabAtkins> | So most newbies to spec stuff only stick around a few months before going back to doing productive work. ^_^ |
| 15:34 | <TabAtkins> | Heh, my favorite tech reported just faved a "your mom" joke made against me. |
| 15:36 | <flyrock> | cool ! I will remember not to jump ahead and the mix of patience and impatience |
| 15:36 | <flyrock> | and yeah, webdev ! |
| 15:38 | <caitp> | in a few years you can be one of the few, the proud, billionaire lamborghini driving spec editors, with girls chasing you all around the state, if you just remember to keep your patience and impatience in the right balance |
| 15:38 | <TabAtkins> | Hey, hey, we don't know what flyrock prefers, they can have boys chasing them around the state if they want. |
| 15:38 | <caitp> | well sure |
| 15:39 | <flyrock> | lol ! |
| 15:59 | <jgraham> | More to the point, we don't know why these people are chasing flyrock around. Maybe it's to exact vengance for crimes against spec editing. |
| 16:44 | <annevk> | caitp: I'm clearly not a successful spec editor |
| 16:45 | <Domenic> | Did you know? Browsers are supposed to implement a JSON-LD API. http://www.w3.org/TR/json-ld-api/#the-application-programming-interface |
| 16:46 | <Domenic> | Wonder how that got to REC |
| 16:46 | <annevk> | Domenic: you're being sarcastic right? |
| 16:46 | <Domenic> | indeeeed |
| 16:46 | <annevk> | It's been a long day |
| 16:47 | <annevk> | As I said to someone else earlier, it's nice how now it's renamed from RDF to LinkedData or JSON-LD, it still doesn't make much sense |
| 16:53 | <jamesr___> | https://dvcs.w3.org/hg/json-ld/raw-file/default/test-suite/reports/cr-20131022.html#test-subjects |
| 16:54 | <jamesr___> | two of the "interoperable implementations" are the same javascript library running in a browser and running in node.js |
| 16:54 | <annevk> | Is it interoperable because the browsers are different? |
| 16:55 | <jamesr___> | afaik running in a browser is 1 and running in node.js is 2 |
| 16:56 | <jamesr___> | unclear if running in a different browser would count as 3 |
| 16:56 | <annevk> | That's some creative accounting right there |
| 16:56 | <annevk> | MikeSmith: ^^ |
| 17:03 | <annevk> | Domenic: shall I open an issue for an OpaqueStreamReader class of sorts? |
| 17:20 | <annevk> | Domenic: see WHATWG email instead |
| 17:20 | <annevk> | flyrock: https://annevankesteren.nl/2014/03/contributing-to-standards has some pointers |
| 17:25 | <flyrock> | thanks annevk :) |
| 17:48 | <TabAtkins> | That... implementation counting is 100% wrong. Multiple implementations *by the same person* dont' even count as separate; running the *same code* in two places absolutely doesn't. |
| 17:48 | <TabAtkins> | I know, this isn't anything surprising, but this sort of gaming just disappoints me. |
| 17:49 | <TabAtkins> | It's like, yeah, I know nobody likes what y'all are doing, but at least have some self-respect. This is sad. |
| 17:50 | <jamesr___> | TabAtkins: another one of the impls is a python lib by the same author as the "2" js ones |
| 17:51 | <TabAtkins> | Yeah, doesn't count. |
| 17:51 | <TabAtkins> | We didn't let Rik's multiple implementations in several browsers count for one of the Adobe-driven CSS specs. |
| 18:03 | gsnedders | wonders what's going to happen to bug tracking for Chromium/Blink when GCode closes |
| 18:11 | <TabAtkins> | What kind of monster puts the sentence-ending period *inside of* the <a> element wrapping the last word in the sentence? |
| 18:17 | <TabAtkins> | The same kind of monster that eschews the Oxford Comma, that's who. |
| 18:49 | <TabAtkins> | The perils of hand-editting a generated file: ToC and headings drift apart. In https://w3c.github.io/FileAPI/TR.html, "Blob Parameters" (8.3.4.7) is missing from the ToC, the following "Determining Encoding" (8.4) is listed as an h3 but styled as an h4, and the following "Events" section is either 8.5 or 8.5.10, depending on whether you believe the heading |
| 18:49 | <TabAtkins> | or the ToC. |
| 19:42 | <MikeSmith> | annevk: seems legit |
| 19:42 | <MikeSmith> | will find out who Director'ed that |
| 19:52 | <hober> | but who Directors the Director? |
| 19:54 | <annevk> | Domenic: binary stream seems like a weird term to use, byte stream seems more accurate |
| 19:55 | <Domenic> | annevk: that is what I use? |
| 19:55 | <annevk> | Domenic: e.g. https://streams.spec.whatwg.org/#model mentions binary; my suggestion in the issue was to change that |
| 19:55 | <Domenic> | ah i see |
| 19:56 | <Domenic> | busy fixing my build process right now... i uncovered some very subtle bug in jsdom and the "proper" way to fix it led me to fixing our xml support... (ecmarkup depends on jsdom) |
| 19:57 | <annevk> | heh, good luck |
| 20:10 | <wanderview> | Domenic: when does (or did) fetch body streams hit chrome release? |
| 20:15 | <Domenic> | wanderview: Chrome 43, so since 42 just released ~6 weeks |
| 20:16 | <wanderview> | Domenic: ok, thanks... trying to get an idea how soon I need to do this system benchmark beyond ASAP |
| 21:55 | <Domenic> | TabAtkins: how do I fix my HTML reference? When I do `Link Defaults: html5 (dfn) structured clone` it gives the wrong spec and when I say `html` instead it gives `No 'dfn' refs found for 'structured clones' with spec 'html'` |
| 21:57 | <Domenic> | TabAtkins: also what happened to CSSWG specs using up-to-date references? They are all to /TRash URLs now |
| 21:57 | <TabAtkins> | HTML5 should be html.spec.whatwg.org. What do you want for it? |
| 21:58 | <Domenic> | It is not |
| 21:58 | <Domenic> | https://streams.spec.whatwg.org/#index-defined-elsewhere |
| 21:59 | <TabAtkins> | It certainly is in the linking database. |
| 21:59 | <TabAtkins> | Oh, [[HTML5]] |
| 21:59 | <Domenic> | No |
| 21:59 | <Domenic> | [[HTML]] works |
| 21:59 | <Domenic> | but in link defaults I have the problem described |
| 21:59 | <Domenic> | So my document is mostly html.spec.whatwg.org but any cross-reffed terms end up referring to the fork |
| 22:00 | <TabAtkins> | Unfortunately, that's the biblio ref for "HTML5" in SpecRef. :/ |
| 22:00 | <TabAtkins> | I'd have to verify, but I think if you manually specify a biblio reference in a <pre class=biblio> it'll override the default data. |
| 22:01 | <Domenic> | Does Link Defaults and [[bracket syntax]] use the same mapping? |
| 22:01 | <TabAtkins> | And the Index generation kinda just guesses that the shortname will match an appropriate biblio ref. The naming bullshit around the HTML fork is messing this up. |
| 22:01 | <TabAtkins> | No, Link Defaults is about linking, using the linking database (it just defaults some of the link attributes on certain terms). [[foo]] is a biblio, using the biblio database. |
| 22:01 | <Domenic> | ok |
| 22:01 | <TabAtkins> | The two are separate for practical and historical reasons. |
| 22:02 | <Domenic> | can we add to/fix the linking database? |
| 22:02 | <TabAtkins> | Yeah, PR the SpecRef project on GitHub. |
| 22:03 | <Domenic> | I think I see |
| 22:03 | <Domenic> | I think html is supposed to work |
| 22:03 | <TabAtkins> | github.com/tobie/specref/ |
| 22:03 | <Domenic> | But it is missing structured clone |
| 22:03 | <TabAtkins> | Rather, there *is* no spec named "html" in the linking database. |
| 22:03 | <TabAtkins> | It's called html5 there. |
| 22:03 | <Domenic> | no there is one |
| 22:04 | <Domenic> | https://github.com/tobie/specref/blob/master/xrefs.json#L1626 |
| 22:04 | <TabAtkins> | That file's irrelevant. |
| 22:04 | <TabAtkins> | Bikeshed doesn't use Tobie's xrefs, just the biblio. |
| 22:04 | <TabAtkins> | It uses its own linking database, generated by Shepherd. |
| 22:04 | <Domenic> | oh damn |
| 22:04 | <TabAtkins> | Heh, sorry. |
| 22:05 | <TabAtkins> | You can check it by going to bikeshed/bikeshed/spec-data/anchors.data |
| 22:05 | <Domenic> | ok, so, can we get Shepherd to work better? |
| 22:05 | <TabAtkins> | Yeah, lemme see if I can tweak it to call the spec "html". |
| 22:05 | <Domenic> | does Shepherd have any entries for html.spec.whatwg.org? |
| 22:06 | <TabAtkins> | Yeah, that's what I'm saying. Shepherd *only* parses the real HTML spec. All the linking database entries are for it. |
| 22:06 | <Domenic> | Then why did https://streams.spec.whatwg.org/#index-defined-elsewhere happen |
| 22:06 | <TabAtkins> | I already explained it. ^_^ The Index generation sorta just hopes that the linking shortname is also the correct biblio reference. |
| 22:06 | <Domenic> | Ahhh yes was just connecting the dots |
| 22:06 | <TabAtkins> | Because, unfortunately, there's no explicit connection between the two databases. |
| 22:07 | <Domenic> | ok sweet |
| 22:07 | <TabAtkins> | That's why some of the CSS refs in the index don't work; the biblio name for them doesnt' match their shortname yet. |
| 22:08 | <TabAtkins> | And it's annoying to mess with SpecRef there, because it does automated dumps of biblio refs from the TR.xml generated by the W3C, so if I change things it'll just revert itself later. |
| 22:08 | <TabAtkins> | Need to figure out how to get around that. |
| 22:08 | <TabAtkins> | Really, I probably just need to check Shepherd's spec data first; it's less complete (won't generate quite as high-quality of a biblio entry), but it's synced with the linking database names. |
| 22:10 | <Domenic> | Well we've got two suffering specs now so no pressure :P |
| 22:10 | <TabAtkins> | I know, I know. File an issue on me or I'll forget. |
| 22:13 | <Domenic> | I often want to add you to the WHATWG GitHub org just so I can assign issues to you |
| 22:13 | <TabAtkins> | Do it? |
| 22:13 | <Domenic> | Sounds good |
| 22:13 | <Domenic> | I'll also file a Bikeshed issue |