| 08:55 | annevk | wonders what decade microformats.org will be on HTTPS |
| 08:58 | <zcorpan> | annevk: jgraham: https://twitter.com/zcorpan/status/1181855911570280448 |
| 08:59 | <annevk> | zcorpan: good luck |
| 09:17 | <jgraham> | zcorpan: If someone provides a script to run curl against a checkout of wpt I expect we can add that to the ci configuration somehow |
| 09:18 | <jgraham> | Do weekly runs or somesuch |
| 09:18 | <jgraham> | (just for those tests ofc) |
| 09:51 | <zcorpan> | jgraham: cool! Can you follow up with Daniel? I gave some pointers in the twitter thread |
| 10:01 | <jgraham> | I don't think I have any way to follow up with Daniel. Well apart from email I suppose |
| 10:02 | <jgraham> | And per twitter he's still doing the boring "their url spec" thing rather than engaging productively |
| 10:12 | <annevk> | TabAtkins: in Encoding I get "FATAL ERROR: Multiple local 'attribute' <dfn>s for 'TextDecoderCommon' have the same linking text 'encoding'." |
| 10:13 | <annevk> | TabAtkins: now TextDecoderCommon does have an internal slot called encoding and an attribute with the same name, but the attribute is annotated with attribute in its <dfn> |
| 10:15 | <annevk> | TabAtkins: and it was building yesterday which makes the recent changes to Bikeshed suspect |
| 10:19 | <annevk> | TabAtkins: filed https://github.com/tabatkins/bikeshed/issues/1537 |
| 12:31 | <annevk> | littledan: why would an Agent flag be passed down to JS? |
| 12:31 | <annevk> | littledan: doesn't JS have access to its Agent? |
| 12:32 | <littledan> | annevk: It would be; it would just *also* be passed down to JS in the dynamic import case |
| 12:32 | <littledan> | and JS and Wasm would need to duplicate the checks |
| 12:32 | <littledan> | so I think the check logically makes more sense in the SW/HTML specs |
| 12:36 | <annevk> | littledan: ah yeah, I keep forgetting the dynamic import case and I suspect Shu might have too |
| 12:36 | <littledan> | are there any problems with the [[Async]] approach? |
| 12:37 | <annevk> | littledan: is that in the current PR? I found the current PR weird because it directly peeks at [[PromiseState]] |
| 12:37 | <littledan> | annevk: That's a separate issue. That's due to an editorial decision Domenic strongly encouraged me to take. I could revert it if you'd like |
| 12:39 | <littledan> | but I guess we took that decision when we were assuming that ServiceWorker would just wait for the TLA to happen |
| 12:42 | <annevk> | littledan: I guess I lost the plot a bit, but if what ljharb is objecting to is the status quo of the proposal I think I'm okay |
| 12:42 | <annevk> | littledan: that is, it seems best for developers if the error surfaces as early as possible |
| 12:43 | <Domenic> | I agree a parsing error is better |
| 12:44 | <littledan> | (I'm also skeptical of this kind of lazy error) |
| 12:45 | <littledan> | annevk: Yeah, many people in TC39 encouraged the ServiceWorker group to reconsider the restriction on async modules, but understood that it was also a decision that W3C/WHATWG can make. In the HTML PR, I included a note encouraging caution in making the restriction. |
| 12:46 | <littledan> | I think we should've been a little more active in the presentation in encouraging people to have some more appreciation for the good technical work going on in other venues, but it's a little tricky rhetorically |
| 12:50 | <annevk> | I find it interesting how folks in TC39 can both appreciate JavaScript not having much API surface and therefore being useful in many contexts and then not appreciating that when they add more surface it might be less generic |
| 12:50 | <annevk> | It's probably not the same people |
| 13:00 | <annevk> | littledan: I added a comment that hopefully helps Shu |
| 13:08 | <annevk> | Domenic: also have a theory for the logo failures now; Firefox doesn't support crossorigin for rel=icon I'm pretty sure, might not even be part of the standard |
| 13:33 | <Domenic> | Ah that makes sense why the logo might be consistently borked, interesting |
| 13:34 | <Domenic> | And I guess the image cache is causing it to break the <img> (although I doubt the spec uses the image cache for <link>) |
| 13:34 | <Domenic> | I still think HTML being inconsistent with other specs is a good hypothesis for styles. Styles are the really bad problem IMO. |
| 13:35 | <annevk> | Happy to patch that in a bit |
| 13:35 | <annevk> | That rel=icon doesn't use the image cache is more a result of image loading not being fully defined than anything else I suspect |
| 13:43 | <annevk> | Domenic: https://github.com/whatwg/html/pull/4994 |
| 17:35 | <ondras> | hm, does mkwst visit here from time to time? |
| 21:14 | <TabAtkins> | ondras: Yes, tho pinging him on Twitter might be more reliable. |