| 00:57 | <Domenic> | jmdyck: thanks, fix PR sent (https://github.com/whatwg/html/pull/11671). BTW do you think the algorithm PR might be ready to land before my retirement (a week from today)? |
| 01:32 | <jmdyck> | hm, dunno, but I'll bump the priority. I'm in the middle of updating to the new main. |
| 04:52 | <annevk> | foolip: pretty sure fetch was always fetch |
| 05:10 | <foolip> | What's that API? |
| 05:18 | <sideshowbarker> | annevk: when you have minute, please take a look at the latest updated https://github.com/mdn/content/pull/41127/files and either post a comment or lemme know whether it’s now OK |
| 05:21 | <annevk> | sideshowbarker: it seems fine to me. I don't really know conventions that well about documenting non-conforming behavior. |
| 05:22 | <sideshowbarker> | yeah that part is a gray area but I think as far as that goes that patch is in line whatever existing conventions we have there |
| 09:32 | <Noam Rosenthal> | Reporting API: https://w3c.github.io/reporting/#idl-index But I see now that we did keep Report, so I don't know what ended up with the web compat issue |
| 09:33 | <Noam Rosenthal> | there was a global element/iframe by that name and a popular page that use the annoying feature of having elements by ID accessible directly from the window |
| 09:34 | <Noam Rosenthal> | Right, if you don't know where you're going you wouldn't get the route change match. |
| 09:35 | <Noam Rosenthal> | (Missed the thread, responded there) |
| 09:35 | <Noam Rosenthal> | We could probably have something like route: unknown or null for these cases, would be a good thing to clarify. |
| 09:36 | <smaug> | Right, since otherwise one would need to have some JS based fallback |
| 09:42 | <smaug> | hmm, though currently does the page even know that there is cross origin traverse about to happen vs someone closing the tab. (I can't recall if navigation API exposes the information. It probably shouldn't, but if it does, too late to change.) |
| 10:05 | <Noam Rosenthal> | I think you get a navigate event with a null destination but need to double-check |
| 10:06 | <Noam Rosenthal> | anyway cross-origin traverses are likely the least interesting use-cases for route-matching... as you can't style anything related to the new route and also can't style links to the route as the back button is not a link, and also the navigation is likely instant because of BFCache |
| 10:10 | <Noam Rosenthal> | ok we only send them for same-origin traverse: https://html.spec.whatwg.org/#preventing-navigation:fire-a-traverse-navigate-event |
| 10:10 | <Noam Rosenthal> | so you also won't be notified of the route change here or of it being a navigation at all... it's like a "close" |
| 12:01 | <Noam Rosenthal> | https://issues.chromium.org/issues/40892121 |
| 12:01 | <Noam Rosenthal> | That's why Report doesn't have an interface object exposed in window:https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/frame/report.idl;l=8;bpv=1;bpt=0 |