05:42
<MikeSmith>
only now noticing that Matrix generates and depends on invalid URLs like https://chat.mozilla.org/#/room/#mdn:mozilla.org (that have another # in the fragment part)
09:26
<MikeSmith>
folks here planning to attend any particular TPAC meetings today? Or dropping in on any?
09:27
<MikeSmith>
anything look especially interesting today on any agendas?
09:28
<MikeSmith>
I guess I will be lurking ing the Service Workers and Web Performance meetings anyway
09:28
<MikeSmith>
ah wait, no Service Workers today; just Web Performance
10:29
<annevk>
yoav: do you recall where that thread was with Artur Janc et al about CORP, CORS, and metadata?
10:29
<annevk>
Oh maybe it was via email
10:30
<annevk>
yoav: https://lists.w3.org/Archives/Public/public-webappsec/2020Jul/thread.html#msg5
10:30
<yoav>
indeed https://lists.w3.org/Archives/Public/public-webappsec/2020Jul/0005.html
10:33
<annevk>
yoav: I guess for the thing later today https://lists.w3.org/Archives/Public/public-webappsec/2020Jul/0012.html captures my feelings pretty well, as well as https://lists.w3.org/Archives/Public/public-webappsec/2020Jul/0013.html (did you invite Camille?)
10:33
<yoav>
yup
10:36
<yoav>
From my perspective, we don't have to solve metadata (beyond size) today, as no RT feature exposes it
10:37
<yoav>
there are feature requests that would need that resolution, but that's less urgent than what's already shipping
10:39
<annevk>
I think we should be careful with setting developer expectations though
10:40
<annevk>
Spectre-only yesterday, sizing today, and all metadata tomorrow would not be a good look
12:50
<zcorpan>
Domenic: annevk: how do i address "using a method of iteration which does not trigger developer-modifiable array accessors or iteration hooks"? https://html.spec.whatwg.org/multipage/urls-and-fetching.html#start-intersection-observing-a-lazy-loading-element
12:51
<annevk>
zcorpan: with a low-level primitive?
12:51
<zcorpan>
annevk: any spec language that doesn't need an "XXX" wrapper
12:52
<annevk>
zcorpan: my question was somewhat rhetorical
12:53
<zcorpan>
ok :)
12:53
<annevk>
zcorpan: that is, we need a non-JavaScript hook into intersection observer that the intersection observer API builds on and we can too
12:55
<zcorpan>
annevk: ok so the issue I filed on intersectionobserver was closed by https://github.com/w3c/IntersectionObserver/pull/449 , but doesn't address at least .isIntersecting , and it seems also we need a way to enumerate entries with Infra Standard language
12:57
<annevk>
"The {{IntersectionObserver/thresholds}} attribute getter will return"
12:57
<annevk>
That leads me to think they didn't really address your issue 🙂
12:57
<annevk>
If they did, there would be internal slots and such to poke at
12:58
<annevk>
(That quote out of context is actually confusing. The problem is that the quote appears in the constructor steps.)
12:58
<zcorpan>
annevk: yeah... https://w3c.github.io/IntersectionObserver/#initialize-new-intersection-observer
13:11
<andreubotella>
annevk: that brain fart was embarrassing
13:27
<zcorpan>
https://github.com/w3c/IntersectionObserver/issues/464
14:39
<annevk>
andreubotella: it isn't really, I had similar thoughts when attempting to address this
20:59
<andreubotella>
> (Registration for public breakouts closed on October 22.)
21:00
<andreubotella>
it doesn't list a timezone though
21:00
<andreubotella>
is it too late?
21:05
<zcorpan>
andreubotella: send an email to dom at w3.org and ask
21:07
<andreubotella>
zcorpan: I'll try that