| 03:47 | <annevk> | jyasskin: sigh, I only looked at bits of WebAuthn |
| 03:48 | <annevk> | jyasskin: can you file an issue? |
| 03:49 | <annevk> | Folks are way too technical debt happy |
| 12:39 | <JakeA> | annevk: How does the DOM handle: "class Foo extends Event {}; new Foo('hi')"? The spec says the event constructor "Returns a new event" |
| 12:40 | <JakeA> | Safari seems to follow that to the letter, and returns an object with the Event constructor |
| 12:40 | <JakeA> | Chrome/Firefox return an object with the Foo constructor |
| 12:44 | <JakeA> | Edge behaves the same as Safari |
| 12:52 | <annevk> | JakeA: I don't really understand how that setup works; presumably it follows from IDL, but it's a little unclear to me |
| 12:52 | <annevk> | JakeA: worth filing an issue on, if only to get test coverage (and maybe an example) |
| 12:53 | <annevk> | JakeA: I think we do have such a test for EventTarget btw, but maybe not all browsers implement that yet |
| 12:53 | <JakeA> | annevk: https://github.com/whatwg/dom/issues/598 |
| 12:54 | <annevk> | JakeA: and dispatchEvent() works fine with it too, I guess? |
| 12:54 | annevk | wonders what else can be surprised here |
| 12:55 | <JakeA> | annevk: It works in all browsers I've tested, but in Edge/Safari you just get an Event object |
| 13:17 | <JakeA> | annevk: The EventTarget thing is a separate issue, right? |
| 13:25 | <annevk> | JakeA: if there's an issue, I guess |
| 13:25 | <annevk> | JakeA: just mentioning it to figure out what we should be saying in general |
| 13:25 | <JakeA> | gotcha |
| 13:27 | <annevk> | Sebmaster: you around? |
| 13:27 | <Sebmaster> | What's up? |
| 13:28 | <annevk> | Sebmaster: Unicode put up a new draft of UTS 46 with updated tests |
| 13:28 | <annevk> | Sebmaster: http://www.unicode.org/draft/Public/idna/11.0.0/IdnaTest.txt |
| 13:28 | <annevk> | hmm |
| 13:28 | <annevk> | Maybe I should be pinging TimothyGu instead ^^ |
| 13:29 | <Sebmaster> | Did they change anything about the actual spec? |
| 13:30 | <Sebmaster> | I could probably poke tr46.js sometime tonight, haven't done any oss work recently |
| 13:30 | <annevk> | Sebmaster: http://www.unicode.org/draft/reports/tr46/tr46.html has the latest diff, doesn't seem substantial |
| 13:31 | <Sebmaster> | Ah, pretty sure we have this in the code already due to test necessity |
| 14:06 | <Domenic> | It looks like they added instructions on how to actually use the test file |
| 14:06 | <Domenic> | And changed the format to be more usable for our purposes |
| 14:06 | <Domenic> | It would be nice to verify that the updates were aligned with what we were hoping for, and if so, tell them |
| 14:07 | <annevk> | Domenic: yeah, I updated the relevant whatwg/url issue, Timothy will have a look next week hopefully |
| 14:08 | <annevk> | Domenic: I created https://github.com/w3c/web-platform-tests/pull/4504 once, but I never really figured out what the underlying issues were |
| 14:08 | <Domenic> | I think TimothyGu did some magic to either the implementation or the test runner to make tr46.js pass all the tests |
| 14:09 | <Domenic> | We should figure out how to port that to WPTs |
| 14:09 | <annevk> | The main problem here is lack of browser interest to fix anything |
| 14:10 | <annevk> | E.g., ToASCII of ASCII vs non-ASCII input |
| 14:10 | <Domenic> | Yeah |
| 14:10 | <Domenic> | I dunno, maybe WebKit cares |
| 14:10 | <Domenic> | Still nice to have tests in case any of them wake up |
| 14:10 | <annevk> | E.g., getting Chrome and Edge to deal with "nontransitional" |
| 14:11 | <annevk> | Domenic: even Safari has weird bugs, where they flip the nontransitional bit depending on which API you use... |
| 14:11 | <Domenic> | Maybe worth filing those |
| 14:11 | <annevk> | These are all filed |
| 14:11 | <Domenic> | Ah OK |
| 14:11 | <annevk> | They're just not getting any attention |
| 23:54 | <Sebmaster> | annevk: are you aware of where the new idnatest.txt is? It's not here yet: https://unicode.org/Public/idna/ |