| 02:22 | <MikeSmith> | TabAtkins: I remain curious what’s special about the IDL in the Web Audio that causes so much errors |
| 02:23 | <MikeSmith> | https://github.com/WebAudio/web-audio-api/issues/2185#issue-588835836 |
| 02:27 | <TabAtkins> | Stuff around heavy references to arguments, which have always been weird. Definitely a Bikeshed bug. |
| 02:31 | <MikeSmith> | OK |
| 02:47 | <MikeSmith> | Chromium question: given a commit hash, how can I tell what release it first shipped in? |
| 02:48 | <MikeSmith> | in the past I have seen links to https://storage.googleapis.com/chromium-find-releases-static/ URLs which show that |
| 02:48 | <MikeSmith> | example: https://storage.googleapis.com/chromium-find-releases-static/ab5.html#ab5ae32c6233fe7938b9a0b53cf1c74918310d7a |
| 02:49 | <MikeSmith> | https://storage.googleapis.com/chromium-find-releases-static/6c2.html#6c2d80337cb1988e53ae29f7418b52e9d81dec8e |
| 02:49 | <MikeSmith> | https://storage.googleapis.com/chromium-find-releases-static/009.html#00971f38908388728f49cd5127b9c6c6761d035f |
| 02:50 | <MikeSmith> | aha |
| 02:50 | <MikeSmith> | nm |
| 02:50 | <MikeSmith> | figured it out |
| 02:51 | <MikeSmith> | dunno if there is so frontend that will it for you, but I realize now you need to replace the NNN.html part with the first three characters of the hash |
| 05:03 | <Domenic> | MikeSmith: https://omahaproxy.appspot.com/ |
| 05:03 | MikeSmith | looks |
| 05:04 | <MikeSmith> | ah beautiful |
| 05:04 | <MikeSmith> | exactly what I was looking for |
| 05:04 | <MikeSmith> | Domenic: thanks much! |
| 05:04 | <MikeSmith> | that omahaproxy names sounds familiar now |
| 06:48 | <annevk> | This declarative shadow DOM thread is something |
| 10:14 | <yoav> | annevk: question regarding monkey patching. Is something like https://w3c.github.io/performance-timeline/#dfn-frozen-array-of-supported-entry-types OK from your perspective (e.g. extending HTML-defined objects to add new objects associated with them)? |
| 10:15 | <yoav> | I know that algorithmic monkey-patching is something we should avoid if possible, but less sure about this one |
| 10:45 | <annevk> | yoav: why are we bringing back hasFeature()-style APIs? |
| 10:45 | <annevk> | (That's not what you asked for, but that would be my main concern with this API.) |
| 10:51 | <annevk> | Domenic: https://github.com/annevk/spec-factory is my initial take, it can do updates fairly well, but some repositories are more custom than anticipated (e.g., Streams has a pretty custom .pr-preview.json and Compatibility calls its main file compatibility.bs rather than compat.bs) |
| 11:19 | <yoav> | it's something we added a while back: https://github.com/w3c/performance-timeline/issues/77 |
| 11:21 | <yoav> | there's also https://dom.spec.whatwg.org/#dom-domtokenlist-supports |
| 12:28 | <annevk> | yoav: did that end up working out? |
| 12:55 | <yoav> | annevk: yeah |
| 12:55 | <yoav> | annevk: thoughts on the original question? is it OK to extend HTML defined objects with associated objects? |
| 12:56 | <yoav> | (outside HTML) |
| 12:59 | <annevk> | yoav: that seems okay, did bz's issue ever get addressed? |
| 12:59 | <annevk> | yoav: it's also a bit vague as to which globals might support which strings |
| 13:02 | <yoav> | yeah, I believe https://github.com/w3c/performance-timeline/pull/133 fixed it |
| 13:06 | <yoav> | yeah, I guess the registry could've defined which entries are e.g. not supported in WorkerGlobalScope |
| 14:41 | <annevk> | Domenic: "GitHub UI does not follow renames" what does that mean? |
| 14:42 | <Domenic> | annevk: when you go to the commit history page for a renamed file you only see commits since the rename |
| 14:42 | <annevk> | Ah yeah, though GitHub's blame is fine with it |
| 14:42 | <annevk> | Domenic: and we encourage https://github.com/whatwg/compat/commits over specific files, right? |
| 14:43 | <Domenic> | True, I suppose |
| 14:43 | <annevk> | I think you had to deal with this too as our build script scans for the .bs file rather than using {shortname}.bs |
| 14:44 | <annevk> | It'd no longer have to do that with this rename (we had more of this before I think) |
| 14:44 | <Domenic> | Yeah I thought some things did index.bs |
| 14:45 | <Domenic> | Ah yeah console and streams do index.bs |
| 14:45 | <Domenic> | Maybe spec-factory can scan for index.bs instead |
| 14:45 | <Domenic> | s/scan for index.bs/scan for .bs/ |
| 14:51 | <annevk> | Yeah, that would create slightly less churn |
| 15:07 | <annevk> | Domenic: oh so Compatibility's .pr-preview.json file is also wrong as it points to compat.bs rather than compatibility.bs |
| 15:07 | <annevk> | Domenic: I should have written this tool ages ago |
| 15:07 | <Domenic> | Heh, nice |
| 15:11 | <TimothyGu> | annevk: would you happen to know who at Mozilla to contact for https://github.com/w3c/fxtf-drafts/pull/395? |
| 15:14 | <annevk> | TimothyGu: I'd try emilio |
| 15:37 | <TimothyGu> | annevk: cool thanks |
| 15:59 | <annevk> | Domenic: hmm HTML's .editorconfig does have specific indentation rules for [source] so your editor might be off |
| 16:06 | <Domenic> | Ah boo |
| 16:06 | <Domenic> | annevk: what do you mean by "associate agents and agent clusters directly"? We add the agents to agent clusters, which seems pretty direct |
| 16:24 | <annevk> | Domenic: 1) I was wondering if the agent cluster had to exist first 2) I was wondering if the agent needs a pointer to the agent cluster (how also do you get to it?) |
| 16:24 | <annevk> | Domenic: as I said though, we can wait with this until shu et al get to it |
| 16:25 | <Domenic> | Ah yeah, we're using a bit of magic spec language with "the agent cluster that contains the agent" |
| 16:25 | <shu> | annevk: this week's TC39 so time's going to be hard. is there an issue with background i can push onto my queue? |
| 16:25 | <Domenic> | Also, I'm thinking of removing "responsible event loop" now as you can go with global object's relevant agent's event loop. |
| 16:25 | <Domenic> | shu: I don't think it's urgent; if we crystallize what we want we can file an issue or PR on ES. |
| 16:26 | <shu> | sgtm |
| 16:26 | <Domenic> | I might do a PR for the explicit realm -> agent pointer soon |
| 16:26 | <Domenic> | I guess I'll leave "responsible event loop" but make it an alias |
| 16:27 | <annevk> | Domenic: another thought I had (but didn't investigate) was only having typed agents and no longer having typed event loops (or vice versa) |
| 16:28 | <Domenic> | I think typed event loops are reasonable as a convenience, e.g. saying "If this is a worker event loop" instead of "if this is an event loop whose agent is a dedicated/shared/service worker" |
| 16:56 | <Domenic> | Hmm I wanted to work on streams as my next cleanup but while I'm here I'm tempted to remove responsible document... |
| 16:57 | <Domenic> | Also "responsible browsing context", probably... will file a separate issue for that |
| 17:41 | <annevk> | Domenic: where is EXTRA_FILES configured? |
| 17:42 | <annevk> | Domenic: it seems it should be in .travis.yml, but https://github.com/whatwg/compat/commit/3067cc49b6684017d6637da8969c56e9e084f8be removed that and https://compat.spec.whatwg.org/review-drafts/2019-06/stroked-text.png loads |
| 17:43 | <Domenic> | annevk: Makefile. travis calls the makefile |
| 17:44 | <MikeSmith> | did Location ever have username and password properties? |
| 18:01 | <annevk> | Domenic: but not for review drafts |
| 18:02 | <annevk> | Domenic: oh wait, that also goes through make deploy I guess |
| 18:02 | <Domenic> | Right |
| 18:02 | <annevk> | oh that's weird |
| 18:03 | <annevk> | thanks |
| 19:26 | <annevk> | Domenic: not really working on it atm, but should we move it to db.json potentially or is that too weird? |
| 19:27 | <annevk> | Domenic: extracting it from the Makefile is kind weird, but doable I suppose |
| 19:27 | <Domenic> | annevk: move what, EXTRA_FILES? I would rather keep it in the makefile. |
| 19:27 | <annevk> | kinda |
| 19:28 | <annevk> | I guess duplication is what I’d be after |
| 19:28 | <Domenic> | If you wanted to add an extra db to spec-factory that seems reasonable I guess |
| 19:28 | <Domenic> | But it shouldn't be the SG's source of truth |
| 19:41 | <annevk> | Anyone have context for https://twitter.com/the1truestripes/status/1245051944558686209? |
| 19:42 | <annevk> | Domenic: yeah okay, I suspect I’ll do that and maybe also open a couple of these Meta: PRs to at least fix some things and get PR templates in more places |
