| 14:42 | <Dominic Farolino> | Basically, but with some fixes and more functionality! |
| 18:38 | <Dominic Farolino> | annevk: Would you be open to changing the formatting style of other WHATWG specs to permit line breaks within phrasing content, like HTML, so the specfmt tool could be used there too? I vaguely recall you saying you'd be open to this but I want to see IIRC |
| 19:29 | <annevk> | Dominic Farolino: let's chat once it's been deployed in HTML CI and has seen plenty of PR activity? |
| 19:30 | <annevk> | But yeah, in principle I'm in favor of automated formatting even if it doesn't meet my preferences. I do wonder how hard it would be to modify to meet my preferences though as inline search is much nicer if you don't have to grep and \s+ everything. |
| 20:18 | <akaster> | Is anyone tracking https://github.com/whatwg/html/pull/9457 ? It looks like it was noted as a "popover spec that should be prioritized" in a WHATNOT a year ago, and we ran into the issues it addresses while implementing popover for Ladybird |
| 20:24 | <smaug> | Dominic Farolino: FWIW the slot reordering case is something like https://mozilla.pettay.fi/moztests/reorder.html . Try to select some parts of the text. Chrome is visually reasonable, but getSelection().toString() is surprising. Firefox has odd visual handling, but reasonable getSelection().toString(). webkit (Gnome web) is like some odd mix of those, in some cases visually good, but getSelection().toString() something I can't quite understand, and in some cases closer to Firefox. |