| 00:47 | <Alan Stearns> | And it looks like we started earlier |
| 07:29 | <annevk> | I think CSS allows commits to main? We don't. |
| 11:36 | <chargeitall> | if the content inserted via ::before or ::after pseudo-elements is indeed semantically important, it should be included in the HTML instead to ensure it is accessible to all users. |
| 17:33 | <TabAtkins> | Ah true, if y'all are all-PR-all-the-time then we're probably still ahead in spirit |
| 20:43 | <snek> | do html or css specify what should happen when different characters of a ligature are styled differently https://gc.gy/aea050d0-8475-4e0e-8324-027a225ddf1d.png (in this case there is a span around the i with a background color applied) |
| 20:45 | <snek> | i didn't see anything in the html spec or css fonts spec but i'm not really sure what i'm looking for 😔 |
| 20:58 | <Alan Stearns> | snek: As far as I know this (and where you might put the cursor as you arrowkey through a ligature) is not defined. And from what I recall Firefox may be the only engine that tries to do something in this case |
| 21:53 | <TabAtkins> | No, this is unspecified. |
| 21:53 | <TabAtkins> | Exactly what you're even capable of doing is dependent entirely on your font rendering engine, so we just don't say anything. |
| 22:57 | <snek> | makes sense, thx |
| 23:05 | <TabAtkins> | WHATWG darkmode PR up at https://github.com/whatwg/whatwg.org/pull/429 ! |
| 23:28 | <TabAtkins> | The specs say that ::before/etc should be highlightable/etc. Firefox does this, Chrome doesn't yet. |
