| 03:11 | <tashasyarifah> | zcorpan: OMG I click the link "individual". I thought the triangle is act for a list. Maybe change the triangle to be more noticeable. I finished filling out the form. Thank you! |
| 03:58 | <Lucy> | π°Don't depend on your salary onlyπ°if you have a Gmail account,computer or smartphones,you can start earning $4,000 daily and $10,000 weekly,without #sending_money to anyone click on the link to get started ππππππππ TELEGRAMπππ₯π₯ https://t.me/+T5bSreXpWsAwMDA0 ADMIN: https://t.me/Braddocklucy |
| 06:20 | <hsivonen> | (FWIW, I don't have any real answers here. Happy to approve a rename to .tentative, or maybe delete the test and open a whatwg/html interop issue so we can investigate and come up with what the answer should be.) |
| 07:29 | <hsivonen> | This test seems to expect non-initial about:blank (which in Chrome fires its load event async) to have the magic characteristic of the DOM getting built (i.e. contentDocument.body existing) synchronously when the location has updated: https://github.com/web-platform-tests/wpt/blob/ab53b6abd671656733e41ef03cd0be11250688d7/content-security-policy/inheritance/history-iframe.sub.html#L53-L63 Is there a legitimate Web compat need for this magic? |
| 11:49 | <Ms2ger ππ> | Is it ever acceptable to use "current settings object" if you're running "in parallel"? cc Domenic annevk |
| 14:06 | <annevk> | Ms2ger ππ: no, not really; current might have changed |
| 15:40 | <Ms2ger ππ> | https://github.com/w3c/geolocation-api/issues/126 |
| 18:22 | <Dominic Farolino> | hsivonen: In both Chrome & Safari, I'm observing iframe.contentDocument == null syncly after location-navigating to about:blank (from cross-origin doc) |
| 18:41 | <hsivonen> | hsivonen: In both Chrome & Safari, I'm observing iframe.contentWindow.location.href == "about:blank" ? |
| 18:52 | <Dominic Farolino> | hsivonen: Well it would only equal about:blank after the navigation is complete/loaded, right? And that's async, as per what I'm observing. |
| 21:08 | <zcorpan> | Domenic: do you know how css module scripts work (in particular if they always create a new CSSStyleSheet object)? See https://github.com/w3c/csswg-drafts/issues/7002#issuecomment-1146198613 |
| 22:00 | <Domenic> | Domenic: do you know how css module scripts work (in particular if they always create a new |
| 22:05 | <Dominic Farolino> | Kiiiinnda looks like they just always do? https://html.spec.whatwg.org/#creating-a-css-module-script |
| 22:06 | <TabAtkins> | it always creates a stylesheet object, but the ES algo it passes that to only uses that value if you haven't already done a css import from that url. If you have it just grabs the existing value. |
| 22:07 | <TabAtkins> | But it remains that all of this work is observable (such as via a proxy on the CSSStyleSheet prototype, I think), whereas JS module creation is not observable, so the model used by JS isn't great here. |
| 22:08 | <TabAtkins> | It should accept some default steps, rather than just a default object. |
| 22:18 | <Jimbo Moyer> | Can anyone teach me to crack WiFi |