| 00:21 | <Ari Entlich> | Digging around a bit more, this behavior in Firefox appears to be very old. It seems to be have been introduced in 2001, 23 years ago. Here is the associated bugzilla bug, including some discussion of the design: https://bugzilla.mozilla.org/show_bug.cgi?id=108308 . This also gives me more confidence that my assessment is correct. |
| 01:05 | <sideshowbarker> | Safari logs false true for https://jsfiddle.net/9j6wcxqu/2/ |
| 01:20 | <Panos Astithas> | Thanks for the heads up, should I add them to the same meeting as the existing one or in future meetings? |
| 01:20 | <sideshowbarker> | I don’t find anything in the spec that says anything about setting the dirty checkedness flag on all elements in a radio button group after the dirty checkedness has been set on one element which happens to be in that group. Ari Entlich So you probably want to file a bug report at https://bugzilla.mozilla.org/enter_bug.cgi?format=__default__&product=Core&component=DOM%3A%20Core%20%26%20HTML |
| 07:32 | <hsivonen> | annevk: What time will the Feb 22 meeting referred to in https://github.com/whatwg/html/issues/5121#issuecomment-1857601843 be at and how do I get myself invited? |
| 07:40 | <annevk> | hsivonen: they'll join the WHATNOT meeting |
| 07:41 | <annevk> | I think the same one. We should just start with this and hopefully cover everything they want to talk about. |
| 07:41 | <hsivonen> | hsivonen: they'll join the WHATNOT meeting |
| 07:43 | <hsivonen> | WHATNOT isn't findable by the usual search engines. |
| 07:44 | <annevk> | hsivonen: apologies, I thought you were on the invite list. Do you want to join just that meeting? |
| 07:44 | <hsivonen> | hsivonen: apologies, I thought you were on the invite list. Do you want to join just that meeting? |
| 07:45 | <annevk> | hsivonen: invited your corporate account, assume that's the one you use for Google Meet |
| 07:46 | <hsivonen> | hsivonen: invited your corporate account, assume that's the one you use for Google Meet |
| 07:46 | <annevk> | Domenic: how are you feeling today and doing for time? |
| 07:48 | <Domenic> | Domenic: how are you feeling today and doing for time? |
| 08:26 | <annevk> | Ari Entlich: sideshowbarker: this is the relevant requirement I think:
|
| 08:27 | <annevk> | Coupled with these requirements for the IDL attribute:
|
| 08:28 | <annevk> | It seems to me that Firefox is correct. |
| 08:29 | <annevk> | Ooh wait. Actually, it only sets dirtiness for a single element. So I guess Firefox is wrong, though arguably its behavior makes more sense than Chromium/WebKit. |
| 08:31 | <sideshowbarker> | Maybe there was an intervening spec change years ago that inadvertently changed the required behavior? |
| 08:32 | <sideshowbarker> | well, or maybe the Firefox behavior predates when this was first properly specced |
| 08:35 | <hsivonen> | annevk: What in the Web Platform is known to set beStrict to true in https://url.spec.whatwg.org/#idna ? AFAICT, nothing in Gecko does. I'm trying to figure out if ICU4X should support the beStrict = true case. |
| 08:35 | <hsivonen> | (My current thinking is not supporting Transitional processing in ICU4X.) |
| 08:37 | <hsivonen> | Also interesting: https://bugzilla.mozilla.org/show_bug.cgi?id=1788115 |
| 08:38 | <annevk> | hsivonen: validation only; domain to ASCII is intentionally not exported. Maybe file a bug for a note as it seems worth stating explicitly. |
| 08:39 | <annevk> | hsivonen: And good to see those fixed! I think we still need another round with the Unicode UTS46 folks as they made some changes last year, but not all the ones we wanted and they also broke some tests. |
| 08:40 | <annevk> | hsivonen: If you have time to help with sorting that through as part of ICU4X that'd be nice. |
| 08:40 | <annevk> | hsivonen: https://github.com/whatwg/url/labels/topic%3A%20idna |
| 08:43 | <hsivonen> | So beStrict = true is needed for checking content for conformance but not for browser processing of anything? |
| 08:46 | <annevk> | hsivonen: correct. |
| 08:46 | <annevk> | hsivonen: created for validator.nu (and friends). |
| 08:47 | <hsivonen> | I see. I guess now I will have to check how much it costs in binary size to carry around browser-irrelevant data. (At run time, I expect it to cost one ALU register masking operation per input scalar value, so not much.) |
| 09:26 | <hsivonen> | Sad: https://github.com/ogham/dog/issues/75 |
| 09:30 | <annevk> | hsivonen: yeah that's a well-known problem. Though I think still not standardized in TLS even... |
| 09:33 | <hsivonen> | Recurring theme for me: I'm writing a Rust crate that does something that an existing crate does, but hopefully faster. I investigate doing a drop-in replacement shim and I find that the existing crate does more things, but it's not clear to me how well those more things are use-case-motivated. |
| 10:18 | <hsivonen> | Ooh. Now I see the logic in the STD3-special-cased characters. Clearly it's a bad idea to store the STD3-disallowed bit on a per input character basis, and instead one should inspect the output for STD3-disallowed ASCII. |
| 10:24 | <annevk> | TabAtkins: I see Bikeshed now provides tooltips for terms but them disappearing once you want to select text is rather annoying. E.g., navigate to https://xhr.spec.whatwg.org/#ref-for-progressevent%E2%91%A0%E2%91%A4 and hover over "ProgressEvent" at the bottom of the Acknowledgments section. Attempt to interact with the seemingly clickable link and other aspects of the tooltip. |
| 10:25 | <annevk> | I guess this is popover? Hmm. |
| 10:51 | <annevk> | PSA: All WHATWG standards now build Bikeshed on CI instead of api.csswg.org (we still use api.csswg.org for PR Preview however). If you see anything weird please reach out to Domenic and I per usual. |
| 10:53 | <annevk> | As a side effect WHATWG green is now restored across all standards. Just hit refresh. |
| 17:33 | <TabAtkins> | annevk: Argh, it's resetting when you hover over the contained link. Getting these events set up correctly is tricky, sorry about that. I'll file and fix in a bit. |
| 18:09 | <TabAtkins> | annevk: 4.1.2 uploaded with the fix |
| 23:10 | <akaster> | Hmm. For https://github.com/whatwg/html/pull/10085 how should I properly refer to `NavigationHistoryEntry`, which is defined in browsing-the-web, in Location, which is part of nav-history-apis? |
| 23:17 | <akaster> | Eh. Well I got it to make *a* link, but it doesn't seem like the right link in the diff page |
| 23:18 | <akaster> | Oh no, it's the right link. Yay. 🦆 |