| 03:43 | <汪军梁> | I would like to participate in the Chinese translation of the DOM Standard, but I'm sorry I don't know where to start. |
| 06:46 | <annevk> | 汪军梁: heya, I don't think there is an ongoing translation effort for Chinese at the moment, but you can start one. I suggest filing an issue at https://github.com/whatwg/dom/issues/new where you indicate where your work will take place and how people can best contact you and then once it's finished we can add a link from the DOM Standard. Does that sound good? |
| 07:06 | <annevk> | hsivonen: one to bookmark for a future blog post: https://github.com/php/php-src/issues/8360 |
| 07:10 | <hsivonen> | hsivonen: one to bookmark for a future blog post: https://github.com/php/php-src/issues/8360 |
| 07:11 | <Andreu Botella> | Why is PHP using "?" rather than "�"? |
| 09:03 | <annevk> | Domenic: so are cache and blob reads potentially always broken? Seems aborting them might be the least of their problem |
| 09:03 | <Domenic> | Broken in what way? |
| 09:03 | <annevk> | Domenic: in that nothing enqueues stuff from the cache store or the blob store onto a stream |
| 09:04 | <Domenic> | Uh oh... |
| 09:04 | <Domenic> | Blobs look good: https://w3c.github.io/FileAPI/#readOperation |
| 09:04 | <annevk> | Because I'd assume that to be somewhat equivalent to network reads, from a high level, and thus also handle aborting there |
| 09:05 | <Domenic> | I guess the magic for caches is hidden in
|
| 09:05 | <Domenic> | It's assumed that constructs a ReadableStream as part of creating the response. |
| 09:06 | <annevk> | Did you mean https://w3c.github.io/FileAPI/#blob-get-stream? Fetch doesn't invoke that though. |
| 09:06 | <Domenic> | Fetch invokes https://w3c.github.io/FileAPI/#readOperation -_- |
| 09:06 | <Domenic> |
|
| 09:07 | <Domenic> | It's... not horrible, just, we need to take out all the FileReader stuff from that |
| 09:07 | <annevk> | Sorry, my bad. I got thrown off by there being a FileReader involved. |
| 09:07 | <annevk> | Yeah. |
| 09:07 | <annevk> | And it should take some kind of abort signal. :-) |
| 09:08 | <Domenic> | Oh, wait, we don't need to use "read operation", we should just use "get stream" |
| 09:08 | <Domenic> | "read operation" unpacks the stream |
| 09:09 | <Andreu Botella> | Blob handling in "extract" could also use "get stream": https://fetch.spec.whatwg.org/#concept-bodyinit-extract |
| 09:14 | <汪军梁> | 汪军梁: heya, I don't think there is an ongoing translation effort for Chinese at the moment, but you can start one. I suggest filing an issue at https://github.com/whatwg/dom/issues/new where you indicate where your work will take place and how people can best contact you and then once it's finished we can add a link from the DOM Standard. Does that sound good? |
| 09:16 | <annevk> | 汪军梁: thank you for working on one! I'm sure there's many people that will benefit from that being available. |
| 09:24 | <annevk> | Domenic: Andreu Botella: filed https://github.com/whatwg/fetch/issues/1504. Might be able to look at that later today. And then for cancelation it seems ideal if we cancel the I/O activity and then let that bubble up to the stream and promise, but maybe Fetch needs to take ownership of some of that logic still as it indeed appears to do today. Not really sure yet what would be best for the cache. |
| 22:00 | <nicolo-ribaudo> | The HTML spec links multiple times to a "synchronous flag" of fetch (for example, in https://html.spec.whatwg.org/#fetch-a-classic-worker-imported-script), but that anchor doesn't exist in the Fetch specification. Has it been renamed to something else? |