| 20:41 | <Luca Casonato> | wanderview: Am I correct in the assumption that URLPattern.compareComponent will not be part of the shipping of URLPattern in Chrome 95? |
| 20:41 | <wanderview> | correct |
| 20:42 | <wanderview> | its behind a separate flag |
| 20:43 | <Luca Casonato> | cool cool - i'll wait with implementing it in Deno until the discussion has settled then. |
| 20:43 | <wanderview> | Luca Casonato: btw, thanks for all the work you and crowlKats have put into fixing spec mistakes! |
| 20:44 | <Luca Casonato> | has been great fun to implement URLPattern so far by the way - spec is very well written and easy to follow 👍️ |
| 20:44 | <wanderview> | sorry there are so many |
| 20:44 | <Luca Casonato> | oh no worries - its a large spec, so makes total sense |
| 20:44 | <wanderview> | thanks! all readability due to Domenic's review |
| 20:45 | <Luca Casonato> | https://github.com/denoland/rust-urlpattern <- we have a fully spec compliant implementation here now (not chromium compliant yet though 😉) |
| 20:45 | <Luca Casonato> | were planning to ship it flagged in a week and a half |
| 20:45 | <Luca Casonato> | and then stabilize around the time 95 goes beta |
| 20:46 | <wanderview> | wow, awesome! |
| 20:47 | <wanderview> | fwiw, mozilla was asking if there were other implementations on their standards-position repo... I mentioned your work, but didn't know the status: https://github.com/mozilla/standards-positions/issues/566 |
| 20:48 | <Luca Casonato> | it's written in Rust, so mozilla could probably just pull it in for their implementation. i'd be happy to collaborate on that front. i'll leave a comment on the standards position issue. |
| 23:10 | <TabAtkins> | annevk: Could I get an eye on https://drafts.csswg.org/css-cascade-4/#fetch-an-import at some point? I'm trying to define @import on top of Fetch, but there's very little guidance, so I'm mostly just copypasting/tweaking text I'm finding in HTML and hoping I'm doing things correctly. |
| 23:37 | <Andreu Botella (he/they)> | So I'm not an expert on fetch by any means, but there's a few things that stand out to me |
| 23:37 | <Andreu Botella (he/they)> |
|
| 23:39 | <Andreu Botella (he/they)> |
|
| 23:40 | <Andreu Botella (he/they)> | Instead of that, you should set one or more of the optional algorithms that are passed to fetch: "processResponse" if you just need a response, or "processResponseEndOfBody" which will give you a response and a byte sequence. |
| 23:41 | <Andreu Botella (he/they)> | Those algorithms will be run in tasks on the networking task source, with the event loop that corresponds to request's client. |
| 23:42 | <Andreu Botella (he/they)> | And request's client should be a Window's environment settings object, I believe |