| 10:34 | <annevk> | snek: yeah, seems reasonable in the abstract |
| 12:10 | <hsivonen> | annevk: It looks like the reporter of https://github.com/whatwg/html/issues/11782 filed it on Gecko and Chromium but not on WebKit. |
| 12:22 | <annevk> | hsivonen: presumably those reports will be closed as INVALID so it doesn't matter? Or am I missing something? |
| 12:22 | <hsivonen> | (https://bugzilla.mozilla.org/show_bug.cgi?id=2000805 and https://issues.chromium.org/issues/461532443?pli=1 ) |
| 12:23 | <hsivonen> | Mostly a FYI about trying different venues. I closed the Gecko bug. |
| 12:23 | <annevk> | (Also doesn't seem like any of that is high priority for the i18n WG, but I suspect Richard at least still cares about it. And Elika prolly too.) |
| 12:24 | <annevk> | Now that we've made other changes to the HTML parser maybe we should reconsider, but it seems really hard to determine where to draw the line. |
| 16:20 | <annevk> | TabAtkins: seeing a weird warning at https://github.com/whatwg/fetch/actions/runs/19468018147/job/55725474022: "Remote data (2025-11-11 11:44) is more than two days older than local time (2025-11-18 16:17); either your local time is wrong (no worries, this warning will just repeat each time) or the update process has fallen over (please report this!)." |
| 16:21 | <TabAtkins> | Yu, someone just reported it over the weekend, looking into it now |
| 16:49 | <TabAtkins> | Ah, it's a data issue that was triggering an error in the update process (someone left an empty id attribute on their heading). Fixed the spec and am currently verifying the fix in Bikeshed. |