| 11:23 | <Andreu Botella (he/they)> | Hey. Just making sure, there isn't any API (implemented, in the works, or anything) to access the browser's spellchecker and detect misspellings in an input field and get dictionary suggestions, right? |
| 11:47 | <annevk> | Not that I know of |
| 11:54 | <Andreu Botella (he/they)> | I'm looking through a patch in Bloomberg's fork of Chromium that exposes a number of internal details when a context menu opens, and they're probably incorporating the dictionary suggestions into their custom context menu |
| 11:56 | <Andreu Botella (he/they)> | something like that might be very useful to editing tools |
| 14:48 | <TabAtkins> | Unfortunately it's a major entropy leak; we decided we aren't allowed to expose similar in css |
| 14:52 | <Andreu Botella (he/they)> | My thoughts were that it surely would not leak anything more than the union of user agent and locale, but I hadn't taken into account that the user's name and address might be added to the dictionary |
| 17:18 | <annevk> | Does CSS not highlight misspellings? That also gives some information, but you'd have to brute force it. |
| 17:27 | <Andreu Botella (he/they)> |
|
| 17:27 | <Andreu Botella (he/they)> | https://drafts.csswg.org/css-pseudo-4/#highlight-security |
| 17:55 | <annevk> | Hmm, security requirements in the security section rather than in getComputedStyle etc. Hopefully that works out... |
| 20:14 | <Domenic> | Let me double-check... |
| 20:43 | <Andreu Botella (he/they)> | TabAtkins: The image labels in the sidebar in https://drafts.csswg.org/css-writing-modes-4/#text-flow aren't very legible in dark mode |