| 08:05 | <annevk> | andreubotella: nice find on the top-level await PR |
| 08:51 | <annevk> | littledan: so to be clear, I was mainly wondering about the principle that would expose encodeURI and not atob |
| 08:52 | <annevk> | littledan: my preference is to have a smaller starting point as that is what Worklets wanted but didn't get |
| 08:52 | <littledan> | oh, sorry if citing you is inaccurate there |
| 08:53 | <littledan> | hmm, I'll raise the smaller starting point in the next SES call |
| 08:53 | <annevk> | littledan: it's not a big deal, to be clear, and that's appreciated |
| 08:54 | <littledan> | I do think there is something to "the JS spec has been a line for a long time, which has some reality to it". but I understand if this is not a desirable thing to make even more visible. |
| 08:56 | <annevk> | I don't think that's really true for web developers, though maybe Node.js made it more apparent |
| 10:09 | <littledan> | I think it's true in the JS ecosystem of today in general, and web developers participate in that. It bleeds out already. It's legitimate to want to reduce it, but i would say it's already "a thing" |
| 10:10 | <annevk> | littledan: You think most web developers will be able to tell where encodeURI and atob sit? |
| 10:13 | <littledan> | I don't think there are many things that we can say most web developers know |
| 10:14 | <annevk> | Agreed, and they shouldn't have to 😊 |
| 14:04 | <hsivonen> | AFAICT, when focus in in an iframe and the iframe navigates, the new document in the iframe gets focus. Firefox fires a focus event on the newly-loaded doc (roughly when requestAnimationFrame starts firing?). However, Chrome doesn't. However, clicking the iframe fires the focus event in Chrome, which suggests that in Chrome the new doc is in some weird state. |
| 14:04 | <hsivonen> | Demo: https://hsivonen.com/test/moz/navigation-focus/ |
| 14:16 | <hsivonen> | Safari also doesn't fire the event in the iframe but also doesn't fire the event if the iframe is clicked, which suggests that Safari actually considers the navigated iframe properly focused (but without event upon loading) |
| 14:16 | <annevk> | hsivonen: in Different-Site I also have to click in Fx it seems |
| 14:17 | <hsivonen> | annevk: You have Fission enabled, right? |
| 14:17 | <annevk> | hsivonen: yes |
| 14:17 | <hsivonen> | annevk: That's the bug I'm investigating. :-) |
| 14:18 | <annevk> | It seems Chrome somehow does that "weird state" consistently |
| 14:18 | <hsivonen> | annevk: Note how in Firefox with Fission without my patch the focus moves out of the iframe |
| 14:18 | <hsivonen> | That is, in Fission, the outer document changes `activeElement` away from the iframe |
| 14:19 | <hsivonen> | I think both the non-Fission Firefox and Safari behavior are defensible, but the Chrome behavior is weird. |
| 14:30 | <annevk> | hsivonen: Safari TP does the same as Chrome for me |
| 14:31 | <annevk> | hsivonen: Safari non-TP too, for that matter |
| 14:31 | <hsivonen> | annevk: Which OS? I tested release version on Mojave and the latest iPadOS. |
| 14:31 | <annevk> | hsivonen: wait, Safari seems weird, if I alt+tab it does fire |
| 14:31 | <hsivonen> | annevk: I guess I should boot up Big Sur. |
| 14:32 | <annevk> | hsivonen: 10.15.7 (19H2) |
| 14:32 | <annevk> | hsivonen: which is Catalina |
| 14:33 | <annevk> | hsivonen: yeah for both versions of Safari I have to alt+tab away and back for onfocus to say has fired |
| 14:33 | <annevk> | hsivonen: and it doesn't say it has fired for the earlier documents |
| 14:33 | <hsivonen> | That makes sense. |
| 14:33 | <hsivonen> | Let's see what Chrome does on alt-tab. |
| 14:33 | <annevk> | hmm actually, for the first document it has, but then the second one it has not |
| 14:34 | <annevk> | Chrome also seems to react to it |
| 14:34 | <hsivonen> | Yeah |
| 14:34 | <hsivonen> | So the iframe is focused enough for Chrome that alt-tabbing back restores focus. |
| 14:35 | <hsivonen> | I think the non-Fission Firefox behavior makes the most sense for Web devs but I could see the argument why the Safari behavior could be defended. |
| 14:36 | <hsivonen> | Maybe I should make the demo log blur and the number of times focus has fired. |
| 14:41 | <andreubotella> | so apparently Chrome's implementation of FACEs also gets newlines wrong |
| 14:41 | <andreubotella> | hopefully that's not something people already depend on |
| 14:42 | <annevk> | Seems very doubtful |
| 17:07 | <hsivonen> | Filed https://github.com/whatwg/html/issues/6209 about the focus thing. |