| 01:56 | <Domenic> | Does anyone know how to get mistranscriptions corrected in generated W3C bot IRC notes? Who do we contact? |
| 02:04 | <annevk> | Domenic: you can use s/what was minuted/what was said/ |
| 02:04 | <Domenic> | annevk: but if they're already published? |
| 02:05 | <Domenic> | or published as "draft"? |
| 02:05 | <annevk> | Domenic: if the minutes are already published this is harder and you might need the team contact to get corrections in |
| 02:05 | <Domenic> | OK |
| 02:44 | <SimonSapin> | annevk: https://url.spec.whatwg.org/#concept-host-parser used to have a blocklist of ascii characters, right? What happened to it? It looks like IDNA’s UseSTD3ASCIIRules could have the same effect, but URL seems not to use it (beStrict defaults to false) |
| 02:46 | <annevk> | SimonSapin: step 7 |
| 02:46 | <SimonSapin> | duh |
| 02:46 | <SimonSapin> | thanks |
| 02:46 | <annevk> | SimonSapin: it was abstracted as there's another host parser now |
| 02:47 | <SimonSapin> | < and > are not in that list, but https://jsdom.github.io/whatwg-url/#url=aHR0cHM6Ly9leGFtPHBsZS5jb20v&base=YWJvdXQ6Ymxhbms= seems to be an error |
| 02:48 | <SimonSapin> | annevk: another host parser? |
| 02:48 | <annevk> | SimonSapin: https://url.spec.whatwg.org/#concept-opaque-host-parser |
| 02:48 | <annevk> | SimonSapin: </> are probably worth an issue |
| 02:49 | <SimonSapin> | alright |
| 19:23 | <smaug____> | Just curious, have we considered removing details element? |
| 19:23 | <smaug____> | er, not details |
| 19:23 | <smaug____> | dialog |