| 07:11 | <Sacha Greif> | hi all! the State of HTML 2025 survey results are now published: https://2025.stateofhtml.com/en-US/ |
| 08:13 | <zcorpan> | sideshowbarker: HTML's "same origin" I think should generally have a hyphen |
| 08:16 | <sideshowbarker> | yup. It’s always an adjective. And to somebody who isn’t already read-up on web-platform terminology, “same origin policy” more likely is going just be (mis)read as “having an origin policy that is the same” — rather than a “policy that is about stuff that has the same origin” |
| 08:23 | <zcorpan> | Should same origin-domain also be same-origin-domain? |
| 08:24 | <Soy una puta con infección vaginal > | 😁 |
| 08:37 | <sideshowbarker> | I think so yeah. But the multiple-modifiers case is the case where it… kind of all breaks down, and gets annoying. |
| 08:39 | <annevk> | I can see same-origin policy, but A and B have the same origin would be weird if it was "A and B have the same-origin". |
| 08:40 | <zcorpan> | annevk: the spec doesn't use that phrasing. It uses "A is same origin with B" which should be with hyphen |
| 08:40 | <sideshowbarker> | Yeah, that would just be wrong. The hyphen is only for when it’s a modifier. It’s simply that: Modifier needs hyphen, not-modifier does not need hyphen. |
| 08:40 | <annevk> | I think it varies. I agree that in that phrasing I could see us switching to a hyphen. |
| 08:42 | <annevk> | But I think a lot of the concern is addressed by us linking all the terms, which makes things far less ambiguous than hyphens ever could. |
| 08:42 | <sideshowbarker> | True |
| 08:42 | <zcorpan> | "If the URL of the Document object containing the hyperlink being audited and ping URL have the same origin" is correct as-is |
| 08:42 | <sideshowbarker> | But not all specs are as rigorous about linking terms |
| 08:43 | <sideshowbarker> | take a look at https://github.com/w3c/aria/pull/2697 |
| 08:43 | <zcorpan> | My issue is not that the spec is ambiguous, it's more my brain signals a semantic parse error |
| 08:44 | <sideshowbarker> | (which is not about hyphens at all, but instead about using the same non-ambiguous terms consistently — and, making them hyperlinks when you use them) |
| 08:45 | <annevk> | Nice! ARIA could use a lot of refactoring like that. It's generally not very solid about its data model and algorithms. |
| 08:46 | <sideshowbarker> | yeah, it’s been improving a lot, though |
| 10:23 | <sfarre> | foolip this fix to the fullscreen spec has been slushing around for a while, and I just need some info on what needs to happen to making it go in. iirc the spec change not only fixes the issue, but it also does what chrome already does at that step as can be seen here |
| 11:30 | <Jake Archibald> | jarhar: I found a minor bug in Chrome's command implementation. Dunno if I filed it in the correct place https://issues.chromium.org/issues/469115770 |
| 15:03 | <sideshowbarker> | smaug: You able to join the UI Events call (happening right now) |
| 15:03 | <smaug> | ooh |
| 15:03 | <smaug> | just a sec |
| 16:00 | <zcorpan> | sideshowbarker: in uievents
Why are the files .txt instead of .include |