03:38
<shu>
annevk: thanks for the heads up. no concerns on the HTML integration from me
16:19
<Dominic Farolino>
Dominic Farolino: well you could imagine it being exposed to the callback so whoever is writing the callback doesn't need to know about who is subscribing directly
Hmm yeah that is interesting. My gut reaction is that something external like AsyncContext is best to handle this. Exposing things like AC/AS within the callbacks seems potentially useful, but I am not sure how we'd do it. We don't want to store per-subscription state on the Observable itself (see discussion around https://github.com/WICG/observable/issues/22#issuecomment-1804938312). So the alternative would be to somehow set the callback this value to some intangible per-subscription object that holds onto, for now, the signal supplied at subscription time. That seems a little funky though.
16:19
<Dominic Farolino>
I guess another option would be to just invoke the next callback with the signal as the last argument every time, but that seems wasteful and not scalable.
18:54
<Meghan Denny>
spam https://github.com/whatwg/webidl/issues/1412
19:07
<Meghan Denny>
do webidl strings support any escape sequences? doesnt appear so but wanted to verify