| 08:11 | <Domenic> | annevk: is there a way to forward things like blocking or priority through service workers without exposing them on Request? I.e. did you have some fix in mind for the latter part of https://github.com/WICG/priority-hints/issues/69#issuecomment-1322346634 besides adding a public blocking property? |
| 08:12 | <Domenic> | Oh, nevermind, it's kind of obvious how to do that. |
| 08:13 | <annevk> | Right, you can take the private member and copy it to the new request created in the Request constructor |
| 08:16 | <Domenic> | I got confused between init and input. |
| 08:52 | <sideshowbarker> | Jake Archibald: https://stackoverflow.com/questions/74529733/are-all-these-multiple-checks-really-required-to-handle-a-new-service-worker-upd |
| 10:19 | <Jake Archibald> | ta! |
| 10:43 | <sideshowbarker> | ta! |
| 10:43 | <Jake Archibald> | No problem, thanks for flagging it |
| 16:01 | <annevk> | Looking for a reviewer of straightforward Web IDL change: https://github.com/whatwg/webidl/pull/1235 |
| 16:44 | <annevk> | krosylight: thanks for doing the diagram work; many people have asked for that over the years, hopefully this is something we can adopt WHATWG-wide as a thing |
| 16:45 | <krosylight> | krosylight: thanks for doing the diagram work; many people have asked for that over the years, hopefully this is something we can adopt WHATWG-wide as a thing |
| 16:45 | <krosylight> | Some native Bikeshed support would be great indeed |
| 16:46 | <annevk> | There's railroad stuff in Bikeshed for grammars; at one point I made an attempt for URL but it didn't really go anywhere |
| 16:47 | <annevk> | For Fetch there's a request to have a diagram for how the various fetch algorithms call into each other |
| 16:47 | <annevk> | It seems this ER thing can be used there |
| 16:48 | <krosylight> | Mermaid has several more types of diagram support, maybe worth looking at them https://mermaid-js.github.io/mermaid/#/entityRelationshipDiagram |
| 16:50 | <krosylight> | Given that this is an NPM stuff, not sure how Bikeshed could adopt it (if the grammar thing solves), maybe there's some useful Python implementation too |
| 16:54 | annevk | waves hands Wasm |
| 16:55 | <krosylight> | Wasm. That reminds me whether we should get a common Wasm WebIDL parser |
| 16:56 | <krosylight> | (because plinss/widlparser doesn't seem too active) |
| 16:57 | <annevk> | You should chat with TabAtkins I guess whenever they're back from vacation. |
| 16:57 | <TabAtkins> | I was back last week |
| 16:57 | <annevk> | Mermaid's State Diagram looks useful for Fetch |
| 16:57 | <TabAtkins> | But yeah mermaid is unfortunately in js so I can't use it readily |
| 16:58 | <TabAtkins> | And widlparser is still active, is it missing changes? |
| 16:58 | <annevk> | There's some pretty old issues |
| 16:59 | <krosylight> | It's not abandoned, I just looked https://github.com/plinss/widlparser/issues/79, not too old but not too active |
| 16:59 | <krosylight> | Given that Mozilla now has https://github.com/mozilla/uniffi-rs/tree/main/weedle2, maybe we could get some common library finally... |
| 17:02 | <annevk> | (I don't think we necessarily need Mermaid support in Bikeshed btw. Given the state of accessibility in it using <img> seems best at which point dedicated support is somewhat questionable.) |
| 17:03 | <krosylight> | Agreed. Let's revisit when more specs get Mermaid diagrams |
| 17:06 | <annevk> | Having a more actively maintained Web IDL parser would be great though. The issue you pointed to is a month old, but there's others that are over half a year and actively blocking spec changes: https://github.com/plinss/widlparser/issues/70 |
| 17:07 | <krosylight> | (Me looking at webidl2.js issue tracker and feeling guilty) |
| 17:11 | <krosylight> | TabAtkins: If we ever get a wasm library for IDL, how much it would take to replace the current widlparser use, assuming that you have no objection? Is there some widlparser-specific feature dependency? |
| 17:16 | <krosylight> | One argument for a common library is to have a common linter. Currently autokagami bot is applying webidl2.js linter rules to every spec, but it should be more ideal if it could be caught by bikeshed level. |
| 17:16 | <TabAtkins> | I have absolutely no idea how to invite wasm from python |
| 17:16 | <TabAtkins> | But that's the only blocker, I suppose |
| 17:18 | <krosylight> | Wasm is old enough, there should be some established way... |
| 17:20 | <krosylight> | Perhaps this one? (I haven't tried it either): https://github.com/wasmerio/wasmer-python |