| 15:50 | <annevk> | Domenic: I will do the top-level origin keying tomorrow |
| 15:50 | <Domenic> | annevk: awesome, thanks! |
| 15:50 | <annevk> | (I'd tell your colleague directly but I'm not sure we share a chat channel) |
| 15:53 | <Domenic> | Yeah, I'll relay |
| 15:54 | <annevk> | 👍🏻 |
| 18:07 | <andreubotella> | Maybe I'm missing something, but it seems like if an HTML byte stream starts with a BOM but has a meta charset with a different encoding, document.characterSet should be the encoding given in the meta charset. |
| 18:08 | <andreubotella> | All three main browser engines give the "right" result instead. |
| 18:09 | <annevk> | andreubotella: BOM ought to win |
| 18:10 | <annevk> | andreubotella: there are some HTML <> Encoding issues, but thought this was not one of them |
| 18:10 | <Domenic> | This is one of them. https://github.com/whatwg/html/issues/1077 |
| 18:10 | <Domenic> | Also my dupe, https://github.com/whatwg/html/issues/1910, which IMO states the problem nice and clearly (since I wrote it ;)) |
| 18:11 | <annevk> | Ah, ta |
| 18:11 | <Domenic> | And my preferred fix: https://github.com/whatwg/html/issues/1910#issuecomment-254017369 |
| 18:13 | <andreubotella> | Right, I thought if this were a real issue and not me missing stuff, it should've been fixed long ago. |
| 18:16 | <annevk> | Domenic: hmm yeah we should do something like that |
| 18:16 | annevk | wonders if andreubotella is interested |
| 18:16 | <Domenic> | Maybe another task for the wonderful andreubotella? :) |
| 18:20 | <andreubotella> | I guess I could have a go at it |
| 18:22 | <annevk> | 🥳 |