| 01:18 | <domfarolino> | annevk: Finally rebased the lazyload PR and addressed your nit. I've responded to your latest comment as well; once we resolve that and once I file a follow-up issue, I think we might be finished after all. |
| 07:14 | <annevk> | domfarolino: sounds great! |
| 10:20 | <moshevds> | Hi all. I'm discussing a way for wasm-bindgen to allow Webassembly generated with that tool to allow registering event listeners in Service Workers. Because Service Workers require this registration to happen on first execution, it seems that WebAssembly.Instance is the only way to do this. |
| 10:21 | <moshevds> | However, a fear that WebAssembly.Instance might disappear has been raised. What is the best way (or community to ask) for me to get some assurances that there is no intention to remove support for running Webassembly before the window for registering listeners has passed? (By retaining WebAssembly.Instance at least until an alternative exists.) |
| 10:22 | <moshevds> | The issue where we have been discussing this is at: https://github.com/rustwasm/wasm-bindgen/issues/1976 |
| 11:19 | <yhirano> | annevk: https://github.com/whatwg/html/issues/5223 |
| 11:21 | <yhirano> | annevk: currently we're not revealing redirect location, are you concerned about the case where malicious developers uses SAB to extract such secret information through SPECTRE-like attacks? |
| 15:25 | <annevk> | yhirano: yes |
| 15:26 | <annevk> | yhirano: or secrets in other headers or the response body |
| 20:23 | <Domenic> | https://tools.ietf.org/html/draft-ietf-httpbis-rfc6265bis-03#section-5.2 and surrounding sections is pretty fun... look at that deep integration with Fetch and HTML inside an IETF document. |
| 20:25 | <Domenic> | Eh except > The term "origin", the mechanism of deriving an origin from a URI, and the "the same" matching algorithm for origins are defined in [RFC6454]. |