| 07:54 | <annevk> | Yeah, the commits are definitely more curated than the PRs (and we try to make the log fairly scannable as well), though the PRs have a lot more information if you need additional context. |
| 08:00 | <sideshowbarker> | Video link for the triage meeting? |
| 08:04 | <krosylight> | Video link for the triage meeting? |
| 08:04 | <sideshowbarker> | Aha, thanks |
| 08:05 | <smaug> | there is another meeting way later today (or rather, early tomorrow) |
| 08:22 | <annevk> | Yeah, the meeting is in 15h - 22min |
| 08:23 | <annevk> | (I'll be sleeping through it per usual.) |
| 14:22 | <hsivonen> | annevk: Have you noticed https://www.ietf.org/archive/id/draft-ietf-emailcore-as-09.html#name-use-and-validation-in-html- and https://www.ietf.org/archive/id/draft-ietf-emailcore-as-09.html#name-use-of-addresses-in-top-lev ? |
| 14:34 | <annevk> | That's news to me. I'm surprised how it's just a simple description of what HTML does given that J.C. Klensin doesn't appear to like the HTML rules. |
| 19:00 | <Jake Archibald> | annevk: do you know off the top of your head how sandboxed data-url workers are? Are they entirely originless? |
| 19:01 | <Jake Archibald> | Trying to figure out if it's a safe place to run 3p code. Or if there's a benefit of putting a worker in a sandboxed iframe instead |
| 23:44 | <smaug> | jarhar: by any chance, have you checked how often select (size=1) has been used in iframes which are too small to show the whole popup - meaning that in current desktop browsers the popup covers also some of the parent document? |
| 23:45 | <smaug> | (I did find some instances of such cases when we were considering to use content processes for select popup rendering) |
| 23:58 | <smaug> | (the new select would be of course opt-in) |