| 07:09 | <MikeSmith> | zcorpan: I’m looking at https://github.com/whatwg/wattsi/issues/47 now |
| 07:10 | <MikeSmith> | = xrefs.json should include cross-spec definitions |
| 07:10 | <MikeSmith> | > Clicking on a definition in the Dependencies section used to bring up a panel with the references in HTML. |
| 07:10 | <MikeSmith> | can you say precisely which references you mean |
| 07:10 | <MikeSmith> | or just one of them |
| 07:11 | <MikeSmith> | ah I guess all of them |
| 07:12 | <MikeSmith> | when I look at snapshots I don’t see that popups were being generated for those |
| 07:12 | <MikeSmith> | https://html.spec.whatwg.org/commit-snapshots/79151848f8f80bb59d9e7bd469c9c1e4e2e7940a#dependencies |
| 07:15 | <MikeSmith> | at least now we are (still) generating the popops |
| 07:15 | <MikeSmith> | so I just need to figure out why it’s not able to populate them |
| 07:18 | <MikeSmith> | OK those terms are actually all in the xrefs.json file |
| 07:18 | <MikeSmith> | e.g., “strip leading and trailing ASCII whitespace” |
| 07:20 | <MikeSmith> | that is, strip-leading-and-trailing-ascii-whitespace |
| 07:21 | <MikeSmith> | and code-point is in there too |
| 07:21 | <MikeSmith> | etc etc |
| 07:21 | <MikeSmith> | so I think the problem must be in html-dfn.js? |
| 07:54 | <zcorpan> | MikeSmith: ok. I didn't actually debug, just guessed at the cause |
| 07:55 | <MikeSmith> | yeah, glad it turns out the cause is not the wattsi code |
| 07:55 | <MikeSmith> | now looking at the JavaScript |
| 07:58 | <MikeSmith> | but I have only 2 minutes |
| 07:59 | <MikeSmith> | now 1 minute |
| 07:59 | <MikeSmith> | before I get sucked off to something less useful for at least an hour |
| 07:59 | <MikeSmith> | will get back to it after that |
| 08:00 | <MikeSmith> | zcorpan: btw thanks immensely for fixing all the stuff I regressed with move to the multipage-enabled dfn handling |
| 08:01 | <zcorpan> | MikeSmith: thank you for enabling multipage dfn ^_^ |
| 08:19 | <zcorpan> | hmm. wattsi does not emit a <body> tag. so our scripts at the top in body are parsed in head |
| 08:49 | <MikeSmith> | oh |
| 08:50 | <MikeSmith> | well `source` has no <body> tag right? |
| 08:50 | <MikeSmith> | maybe we can fix it just by adding it to `source` |
| 08:51 | <MikeSmith> | zcorpan: btw I mispoke earlier, about the cause of the Dependencies problem not being in wattsi |
| 08:52 | <zcorpan> | MikeSmith: source has body |
| 08:52 | <MikeSmith> | I had just gotten confused about the state of my working copies |
| 08:52 | <MikeSmith> | oh |
| 08:52 | <MikeSmith> | OK well we can fix that <body> thing in wattsi easily enough |
| 08:52 | <zcorpan> | I've PRed already :-) |
| 08:52 | <MikeSmith> | ah cool |
| 08:53 | <MikeSmith> | so about the Depedencies thing, the wattsi fix is dead simple |
| 08:53 | <zcorpan> | sweet |
| 08:53 | <MikeSmith> | - if ((Variant <> vDEV) and (not DFN.HasAttribute(kCrossSpecRefAttribute))) then |
| 08:53 | <MikeSmith> | + if (Variant <> vDEV) then |
| 08:53 | <MikeSmith> | will PR that right now |
| 08:53 | <MikeSmith> | I now do not remember why I put that `and (not DFN.HasAttribute(kCrossSpecRefAttribute)` in there to begin with |
| 08:54 | <zcorpan> | i almost have re-opening panel across multipage working |
| 08:54 | <MikeSmith> | oh wow |
| 08:54 | <MikeSmith> | great |
| 08:55 | <MikeSmith> | yeah in pratice that UX regression is pretty glaring |
| 08:55 | <MikeSmith> | since when actually using the spec, you end up following many dfn links across pages |
| 10:40 | <zcorpan> | man now i might just start to use multipage again |
| 11:00 | <zcorpan> | do updates happen automatically now when merging changes to wattsi (for travis CI, deployment)? Domenic? |
| 11:23 | <Domenic> | zcorpan: for unknown reasons no, the web hook errors out. You have to ssh in. |
| 11:26 | <zcorpan> | Domenic: ok. can you do that for https://github.com/whatwg/wattsi/pull/49 ? |
| 11:44 | <zcorpan> | I want https://discuss.httparchive.org/t/numdomelements-data/756/2 but for <hr> specifically (i.e. REGEXP_MATCH(LOWER(body), r'<hr(\s|>)') or so) |
| 11:45 | <zcorpan> | How do I write a query to count matches for each site? |
| 11:45 | <zcorpan> | what I've tried I think counts number of resources that have <hr> at all, not the total number of <hr>s there is |
| 11:46 | <zcorpan> | igrigorik: ^ |
| 11:47 | <zcorpan> | (checking just where page = url is fine) |
| 15:28 | <salva_> | hi there! |
| 15:29 | <salva_> | Salva from Mozilla here |
| 15:29 | <salva_> | good afternoon from Spain |
| 20:51 | <TabAtkins> | Domenic: Per aklein, the better way to contact tc39 is via their github or mozilla#jslang IRC. |
| 20:51 | <aklein> | TabAtkins: er, or #tc39 on Freenode |
| 20:52 | <aklein> | bterlson created that soon |
| 20:52 | <TabAtkins> | Yeah, I'm in that one. |
| 20:52 | <TabAtkins> | Should probably join moz's IRC. |
| 20:54 | <Domenic> | GitHub is only really for bug reports. |
| 22:59 | <MikeSmith> | anybody here have some experience with Yacy or Solr? |
| 22:59 | <MikeSmith> | I have a Yacy instance set up to index the multipage HTML spec |
| 22:59 | <MikeSmith> | and it successfully indexes all the pages expect just one |
| 23:00 | <MikeSmith> | https://html.spec.whatwg.org/multipage/media.html |
| 23:00 | <MikeSmith> | my Yacy admin console shows it fetched that document successfully and has the raw content |
| 23:02 | <MikeSmith> | but then it shows nothing in the Parsed Content and Parsed Sentences parts of the admin browser for that page |
| 23:02 | <MikeSmith> | whereas for all the other multipage/ documents it shows the expected results of parsing those |
| 23:03 | <MikeSmith> | .. |
| 23:04 | <MikeSmith> | so one thing I’m wondering is, what HTML parser does Yacy use and is it failing on that document for some reason |
| 23:05 | <MikeSmith> | would like to get this figured out, because otherwise we can’t get search results for searches of any text in that /multipage/media.html document |
| 23:34 | <MikeSmith> | https://github.com/yacy/yacy_search_server/blob/master/source/net/yacy/document/parser/htmlParser.java I guess |