| 10:53 | <Noam Rosenthal> | jjaschke (out until Dec 1), smaug, if you're around at TPAC we can perhaps do some navigation API whiteboarding to resolve some of the pending messy issues. I understand farre won't be there unfortunately. Anyone else who's around is welcome of course (e.g. Dominic Farolino) |
| 10:54 | <smaug> | I'll be there |
| 10:56 | <smaug> | I don't think wait-for-all is that messy. The spec is mostly good in that case, and API is part of interop, so "encouraging browsers to precisely match the web standards " 😉 But yeah, that issue, and perhaps others too should be discussed. |
| 10:57 | <smaug> | And we should also discuss about that "encouraging browsers to precisely match the web standards " part. |
| 11:08 | <Noam Rosenthal> | It's messy when there is a divergence between WPTs and spec which in some cases begs the question of which one is correct. |
| 11:09 | <Noam Rosenthal> | anyway, I saw that the process/meta question is already on the agenda requests but what I want is to spend a bit of time on the specifics and make sure we make the right decisions for users/web-devs. |
| 11:10 | <smaug> | Sure. |
| 11:14 | <farre> | I must admit that I'm surprised by the amount of divergence |
| 11:18 | <Noam Rosenthal> | I wasn't involved when it was spec'ed/implemented but I remember that there was a huge hanging PR with a lot of details for quite a while, and the prototype was progressing alongside the spec. So it caught me by surprise as well but also it's not totally unexpected given the complexity of this API |
| 11:18 | <farre> | Or Session History and Navigation in general |
| 11:21 | <Noam Rosenthal> | Yea exactly. I am curious as to whether this is an outlier or there are other recent examples of this kind of divergence/complexity. Answering this can help the meta conversation. |
| 12:26 | <smaug> | Trusted types was perhaps a bit similar, though there through some great collaboration specs and implementations got into a lot better shape. But it did mean filing spec issues and fixing them when the spec wasn't implementable and also writing tests following the spec, not the first implementation. |
| 12:36 | <Noam Rosenthal> | Yea I see that TrustedTypes landed in 2019, and there were some recent spec-alignment changes |
| 12:38 | <smaug> | "some" 🙂 And lots of new tests |
| 12:39 | <smaug> | (I can't thank Frédéric enough for writing tons of tests) |
| 12:40 | <foolip> | annevk zcorpan Jake Archibald: Noam Rosenthal and I are working on streamHTMLUnsafe() and would like to use the stages process, and would like to move https://github.com/whatwg/html/issues/2142 to stage 1. (https://github.com/whatwg/html/issues/11669 is also very relevant, but we don't need two issues in the stages process I think.) |
| 13:43 | <zcorpan> | foolip: SGTM, maybe add to https://github.com/whatwg/html/issues/11711#issuecomment-3432130305 ? |
| 16:42 | <Dominic Farolino> | Yes definitely! Looking forward to this |
| 19:52 | <cwilso> | Draft WHATUP schedule posted :https://github.com/whatwg/html/issues/11711#issuecomment-3499143498 |
| 19:52 | <cwilso> | Please let me know if you need changes, and there are still a few openings. |
| 20:56 | <nicolo-ribaudo> | If there is time available, could we also talk about https://github.com/whatwg/html/issues/11711#issuecomment-3481575249? :) |
| 23:48 | <cwilso> | Gaaah nicolo-ribaudo Andreu Botella (🕑 JST, mostly off until Nov 10) I'm so sorry, I dropped that one. Added in. |
| 23:48 | <cwilso> | Schedule updated with some slight changes per requests: https://github.com/whatwg/html/issues/11711#issuecomment-3499143498 |