| 07:32 | <hsivonen> | annevk: I don't know bidi well enough to reason about the proposed rules and what happens to the attack surface. Anecdotally, the current situation does not seem as bad for Web compat practically as abstract reasoning suggests: So far, there haven't been actual Web compat issues arising from the current rules ending up on my plate to fix, and the reported cases of rejected names were attack host names. I mainly care about not having to make the is_passthrough_ascii_label function at https://github.com/servo/rust-url/blob/main/idna/src/uts46.rs#L143 stricter. The current bidi check is a bit simpler in the sense that one the domain as a whole is found to be a bidi domain, you don't need to care about the positions of the labels to do further checks, but once the checking is triggered, it doesn't seem too onerous to have a bit of extra state to have different rules for different labels such that labels that we'd remember the status of the most recently checked label so that if the label after it a bidi label, we'd do a deferred decision on the status of the label immediately before the bidi label. |
| 07:35 | <hsivonen> | (is_passthrough_ascii_label passes through labels that are ASCII and that will be allowed whether or not the domain ends up being a bidi domain name.) |
| 07:37 | <hsivonen> | Currently my main annoyance is that is_passthrough_ascii_label has to reject 1password and 9to5mac, so the perf is pessimized even though what follows is as plain as .com. But realistically, it's not too bad that these domains don't get the same perf as domains that don't start with a digit. |
| 07:40 | <hsivonen> | These names are still faster to process than various other names that are so fast that IDNA isn't what makes browsers slow anyway. |
| 09:33 | <sideshowbarker> | Anybody know if there’s a channel/room some place where people from different browser engines who work on implementing accessibility/AT/screen-reader support get together to chat? |
| 09:35 | <sideshowbarker> | I mean for the parts of the engine that communicate with the platform-specific accessibility APIs: AX/NSAccessibility on macOS, ATK/AT-SPI2 on Linux, and whatever the names of the equivalent Windows APIs are. |
| 09:36 | <Ms2ger> | Alice (🇳🇱) might know |
| 09:42 | <Alice (🇳🇱)> | if there is I wasn't invited :( but either way we should make a new one |
| 09:44 | <sideshowbarker> | Howdy Alice 🙂 Yeah, let’s figure out a place that’d be agreeable to everybody, and make a room there |
| 09:50 | <Alice (🇳🇱)> | it's an awkward time of day for both east-coast Australia and all of north America but I'll ping some folks and see who'd be interested (and if my invite got lost in the mail for any hypothetical existing space) |
| 09:51 | <sideshowbarker> | No rush, anyway. But looking forward to having it :) |
| 13:05 | <Alice (🇳🇱)> | Splitting this out to a thread just avoid spamming everyone. Jamie Teh didn't know of anything either, and he'd be happy to join. |
| 13:06 | <Alice (🇳🇱)> | We agreed Slack or Matrix would probably be the best platforms; he said Slack is somewhat more accessible for him, but that he also already uses Matrix and finds it ok on desktop other than (ironically) threads |
| 13:06 | <Alice (🇳🇱)> | I'm waiting for the west coast to wake up to ping some WebKit folks :) |
| 13:06 | <Alice (🇳🇱)> | I'm not even sure who I'd ping on Blink any more :( but others may know |
| 13:12 | <sideshowbarker> | I see Joanie touched some ui/accessibility sources in there a couple months back. |
| 13:12 | <sideshowbarker> | Would be great to have Joanie joining, regardless |
| 13:20 | <sideshowbarker> | This is what I find for the top of a |
| 13:22 | <sideshowbarker> | And for |
| 13:42 | <zcorpan> | annevk: for https://github.com/whatwg/fetch/pull/1898 , I've now merged the HTML PR |
| 13:52 | <annevk> | Ok cool, I merged CSP & Fetch |
| 13:57 | <zcorpan> | Thanks! |
| 14:05 | <sideshowbarker> | by the way, this is what I’ve been working on: https://github.com/LadybirdBrowser/ladybird/pull/8603 |