| 09:55 | <Ms2ger> | So, uh |
| 09:55 | <Ms2ger> | W3C bug tracker is shutting down on Monday, and we haven't backed up the IDL issues |
| 09:56 | <Ms2ger> | MikeSmith, you know who I can poke to deal with that, like, today? |
| 10:16 | <annevk> | Ms2ger: will they 404 the lot? |
| 10:17 | <annevk> | I guess either way it's not great |
| 10:17 | <annevk> | We've also not dealt with the HTML backlog I think |
| 10:21 | <Ms2ger> | "A static copy of the contents of this service will be archived and made available in place.", allegedly |
| 10:21 | <Ms2ger> | But probably no search |
| 10:29 | <MikeSmith> | Ms2ger: yeah I'm told all the URLs will keep working |
| 10:30 | <MikeSmith> | but the search feature will not |
| 12:50 | <Domenic> | The search feature is useful for filtering by component |
| 12:51 | <Domenic> | I might spend time on this today depending on what else comes up... |
| 12:51 | <Domenic> | (For HTML) |
| 12:55 | <annevk> | Domenic: are you planning on working on the Twitter integration? |
| 12:55 | <Domenic> | annevk: it keeps sliding off my to-do list :-/ |
| 12:55 | <annevk> | Ah, same here |
| 12:56 | <annevk> | Perhaps in a couple of weeks, but I'm not very familiar with our server setup |
| 15:16 | <Domenic> | annevk: the last step of https://html.spec.whatwg.org/#perform-a-microtask-checkpoint unsets the performing a microtask check point flag |
| 15:16 | <annevk> | Domenic: it does, but the step in spin the event loop that tries to run perform a microtask checkpoint does not get it unset, because it's still set at that point |
| 15:19 | <Domenic> | annevk: I must be missing something. In step 1 of STEL, the flag is set. In step 5 of STEL it calls PAMT. Step 1 of PAMT sets the flag to true, redundantly. Step 5 of PAMT sets it to false. So by the time we reach step 6 of STEL it's set to false, from what I can tell. |
| 15:22 | <annevk> | Domenic: how do you get to step 1 of PAMT? |
| 15:22 | <annevk> | Domenic: you're missing step 0, which is to check the flag |
| 15:22 | <Domenic> | FRRRRRIG |
| 15:22 | <Domenic> | Please fix step 0 |
| 15:23 | <Domenic> | My eyes go straight from bold <dfn> to the nearest 1. |
| 15:23 | <annevk> | Domenic: separately though? |
| 15:23 | <Domenic> | I mean seems reasonable to do it while here but I could fix it right now if you want. I'm really angry at that sentence at the moment :) |
| 15:23 | <annevk> | Domenic: that's fair, I did think about it, but I don't wanna couple too much stuff together |
| 15:24 | <annevk> | haha |
| 15:24 | <Domenic> | OK, let me re-read your comments now. |
| 15:27 | <Domenic> | annevk: another cleanup we should do is that we sometimes set the performing microtask checkpoint flag to true, which is weird since it's a flag. |
| 15:28 | <annevk> | Domenic: yeah, boolean all the things |
| 15:28 | <annevk> | Domenic: I'm converting flags to booleans as I touch them these days |
| 15:28 | <Domenic> | Yeah +1 |
| 16:17 | <innovati_> | Does 'href' officially stand for anything like 'hypertext reference' or similar? |
| 16:25 | <Mek> | that's what https://www.w3.org/Provider/ServerWriter.html claims, yes |
| 17:33 | <innovati_> | Thanks Mek, it looks like that document is from 24 years ago‽ seems authoritative |
| 17:48 | <Domenic> | annevk: I have a patch I'm working on now that gives task a set of fields and makes queue a task more rigorous. |
| 18:23 | <annevk> | Ooh cool |
| 18:24 | <annevk> | HTTP Workshop is most of next week so review might drag out potentially |
| 18:59 | <Domenic> | No problem, I've done it to you enough times ^_^ |
| 21:04 | <AutomatedTester> | what is the expectation of highlighting the rendered text of a web component and the next node e.g. <web component>some text</web component> <div>foo</div> so that it might look like `some text foo` when rendered. If I highlight this to say copy the text, what should be highlighted? Noticed Chrome and Firefox do different things |
| 21:07 | <Domenic> | AutomatedTester: translating mouse-drags into highlighting and selection is not generally covered by specs; that's a browser UI issue. |
| 21:07 | <Domenic> | Does anyone know where that SVG rendering profiles spec is that talks about e.g. when to execute script or not? |
| 21:07 | <AutomatedTester> | oh ok, I thought it might have been a DOM Range thing |
| 21:08 | <Domenic> | AutomatedTester: yeah that would govern what results you get back from the Range API, but not when you drag your mouse. |
| 21:08 | <Domenic> | OK, the spec I was looking for is https://svgwg.org/specs/integration/ . My strategy that the moment I asked for help I would figure it out myself was a great success. |
| 21:13 | <Domenic> | Looks like I'm on track to finish out the HTML bugs but https://www.w3.org/Bugs/Public/buglist.cgi?list_id=70355&product=WHATWG&resolution=--- still has a good amount of MIME Sniffing. |
| 22:22 | <Domenic> | https://www.w3.org/Bugs/Public/buglist.cgi?component=HTML&list_id=70354&product=WHATWG&resolution=--- done |
| 22:50 | <Domenic> | (MIME Sniffing bugs not moved, for the record. Maybe GPHemsley or annevk could help with that.) |
| 22:50 | <GPHemsley> | ohai, I'm actually here in realtime for a change |
| 22:51 | <GPHemsley> | I'll have reassociate myself with W3C Bugzilla, but IIRC I already moved all the mimesniff bugs to github back in the beginning |
| 22:54 | <GPHemsley> | unless I'm thinking of the ticket-moving from IETF to W3C that I also had to do |
| 22:56 | <GPHemsley> | aw, looks like that's what I was thinking of |
| 23:18 | <GPHemsley> | alright, I closed what I could; the rest will need to be handled by someone with more recent association with the spec and the plans for its expansion |
| 23:18 | <GPHemsley> | annevk: https://www.w3.org/Bugs/Public/buglist.cgi?component=MIME&list_id=70360&product=WHATWG&query_format=advanced&resolution=--- |
| 23:19 | <GPHemsley> | (some things may/should have been moved to Fetch) |