| 03:18 | <Domenic> | hmm, dom spec has some animation when clicking on an algorithm (to get the popup where it is referred from) Maybe it has been there for quite some time, but it is a bit annoying |
| 03:19 | <Domenic> | Root cause is https://matrixlogs.bakkot.com/WHATWG/2024-01-26#L2-L3 |
| 03:21 | <Domenic> | Did handling of fragment-only links with a base url change at some point? I recall them being same-document references even if there was a base url, but that has changed? |
| 06:49 | <sideshowbarker> | Has anybody ever run into a problem with bikeshed generating output with yesterday’s date rather than today’s date? I’m running bikeshed locally, and it’s putting 15 February 2024 into the output it’s generating… |
| 06:50 | <sideshowbarker> | When I was doing the exact same thing yesterday, it was putting 15 February 2024 as expected. But that was yesterday |
| 06:53 | <sideshowbarker> | I find nowhere in my build environment where the date would getting persisted somehow |
| 08:17 | <Domenic> | Maybe it's picking UTC dates? |
| 14:19 | <Noam Rosenthal> | zcorpan: how about <link rel=expect idref=foo blocking=render>? It's a tad more verbose, but then we can use IDRefs for future "internal resource links", they don't have to be "expect", and it feels a bit more consistent with links. |
| 14:21 | <Noam Rosenthal> | (rel was never the problem here, it was reusing href) |
| 15:47 | <annevk> | Ms2ger: not entirely sure tbh. Apparently worklets is more complicated than I remembered. |
| 15:48 | <annevk> | zcorpan: don't quite remember, it might need some rethinking |
| 15:50 | <Ms2ger> | Ms2ger: not entirely sure tbh. Apparently worklets is more complicated than I remembered. |
| 15:50 | <Ms2ger> | Please let me know if there's anything I can do to make review easier |
| 19:19 | <annevk> | jfernandez: do you know if ed25519 has been brought to WebAppSec yet? |
| 21:26 | <jfernandez> | Not yet, as far as I known |
| 21:27 | <jfernandez> | From one side, I wanted to wait until blink and WebKit ship it by default, ideally both ed25519 and x25519 |
| 21:29 | <jfernandez> | On the other hand, the spec editor prefers to implement also the Curve488 algorithms and propose both curves altogether |
| 21:30 | <jfernandez> | I don’t agree with that, thought; I think we can bring Curve25519 first |
| 21:40 | <annevk> | jfernandez: I think bringing it to WebAppSec before shipping would be good. Having it in a proper standards setting will help ensure we're all on the same page. I'm at least somewhat hesitant to approve WebKit shipping WICG-only things. |
| 21:40 | <annevk> | jfernandez: FWIW, I agree with you in terms of scope. |
| 21:50 | <jfernandez> | jfernandez: I think bringing it to WebAppSec before shipping would be good. Having it in a proper standards setting will help ensure we're all on the same page. I'm at least somewhat hesitant to approve WebKit shipping WICG-only things. |
| 21:50 | <jfernandez> | But yeah, it’s indeed better to propose it in the WebAppSec as soon as possible |
| 21:52 | <jfernandez> | I’ll take care of it |
| 23:19 | <aja> | FYI https://groups.google.com/a/mozilla.org/g/dev-platform/c/xlLoQdgJy-I |