| 00:15 | <Domenic> | MikeSmith: FYI we'll get the MDN stuff landed before TPAC, that's a good deadline for me. |
| 00:30 | <MikeSmith> | Domenic: super, thanks |
| 00:31 | <MikeSmith> | I think I’m done fiddling with it as far as tweaks I wanted to make to get it review-worthy |
| 00:34 | <Domenic> | \o/ |
| 01:59 | <MikeSmith> | Domenic: FYI https://stackoverflow.com/questions/52771970/use-fetch-streams-api-to-consume-chunked-data-asynchronously-without-using-recur |
| 11:06 | <`slikts> | I rewrote the js-csp ping-pong example using transformstream: https://jsfiddle.net/slikts/0noqL9we/9/ |
| 11:06 | <`slikts> | I'm not really clear on why it produces an error |
| 11:07 | <`slikts> | I mean, why it throws undefined |
| 11:07 | <`slikts> | shouldn't there be an errror message |
| 11:08 | <`slikts> | the error can be from either reader.read or writer.write, and there's no way to tell |
| 11:09 | <`slikts> | also, this is mentioned nowhere, but transformstream is an implementation of CSP in a straightforward sense |
| 11:10 | <`slikts> | and csp is the general abstraction for concurrency in golang and core.async |
| 11:22 | <hsivonen> | what spec are the XML expectations of https://wpt.fyi/results/encoding/utf-32.html?label=experimental based on? |
| 11:25 | <hsivonen> | (It seems to me that Firefox is right and the test is wrong for XML) |
| 11:26 | <hsivonen> | but since the XML tests pass in other browsers, I guess we need to define that is correct for the sake of interop |
| 11:27 | <hsivonen> | but I have a hard time explaining the expectation except by actually sniffing for the UTF-32 BOM (which we don't want to do!) and mapping it to windows-1252 |
| 11:27 | <hsivonen> | same thing at https://wpt.fyi/results/encoding/unsupported-encodings.any.html?label=experimental |
| 11:44 | <annevk> | hsivonen: I've been discussing this with Joshua |
| 11:44 | <`slikts> | "Push sources push data at you, whether or not you are listening for it. They may also provide a mechanism for pausing and resuming the flow of data." |
| 11:44 | <annevk> | hsivonen: https://github.com/web-platform-tests/wpt/pull/13082 |
| 11:44 | <`slikts> | they're not really push sources if you can pause them |
| 11:44 | <`slikts> | it's just an obtuse api for pulling then |
| 11:44 | <`slikts> | push stream can just be sampled from |
| 11:45 | <`slikts> | *a true push stream |
| 11:45 | <`slikts> | if it can be paused/resumed, it can mechanically be transformed to pull |
| 11:45 | <`slikts> | that's from streams spec |
| 11:46 | <`slikts> | a true push stream is, for example, user events |
| 11:47 | <`slikts> | can't pause users |
| 11:47 | <`slikts> | or something based on time, since you can't pause time |
| 11:50 | <hsivonen> | annevk: thanks |
| 11:50 | <`slikts> | should I make an issue about that sentence? |
| 13:55 | <`slikts> | do node streams duplicate whatwg streams? |
| 15:21 | <`slikts> | found the answer: https://github.com/nodejs/node/pull/22352 |
| 15:21 | <`slikts> | seems like NIH on node's side |
| 15:22 | <annevk> | Node way predated these |
| 15:23 | <annevk> | But also had flaws |
| 15:23 | <annevk> | Node may adopt WHATWG streams in the future |
| 15:24 | <`slikts> | that'd be reasonable for interop |
| 15:25 | <`slikts> | a polyfill based on node streams instead of from scratch should also be simple |
| 15:25 | <`slikts> | at a glance anyway |
| 18:34 | <annevk> | This new navigate event is kinda meh, I much rather have some kind of navigate honeypot, whereby you can opt in to handle navigations initiated in other browsing contexts |
| 18:35 | <annevk> | Basically copy some app-functionality to the web, while also continuing to allow for normal navigations |
| 22:00 | <innovati> | Is there a way for JavaScript in the browser to tell if an element is a void tag in HTML? |
| 22:48 | <innovati> | I just tried to find the list by doing tag.outerHTML.toLowerCase().endsWith(`</${tag.tagName.toLowerCase()}>`) === false |
| 23:16 | <MikeSmith> | innovati: why not just check the element name? |
| 23:16 | <MikeSmith> | it’s not a long list |
| 23:17 | <MikeSmith> | area, base, br, col, embed, hr, img, input, link, meta, param, source, track, wbr |
| 23:17 | <MikeSmith> | https://html.spec.whatwg.org/multipage/syntax.html#void-elements |
| 23:18 | <innovati> | I know, but since I wrote a plugin to do that, the list had changed, so I was wondering if there was a way for the browser to determine this for itself |
| 23:19 | <innovati> | I'm also wondering if the browser knows what HTML tags it supports (as I suspect the list of tags it knows about might be greater than HTML) |
| 23:21 | <MikeSmith> | not sure what you mean by “knows” |
| 23:22 | <innovati> | things it could create with document.createElement() |
| 23:23 | <innovati> | the browser already knows about HTML elements |
| 23:24 | <MikeSmith> | document.createElement("foo") |
| 23:24 | <innovati> | there's a lot of combinations to try if you were to do it that way, is there any way you can find out from the browser what it knows about? |
| 23:26 | <MikeSmith> | sorry I still don’t understand what you mean by “knows about” |
| 23:26 | <MikeSmith> | e.g., do you mean the element has an interface other than HTMLUnknownElement? |
| 23:26 | <MikeSmith> | or what? |
| 23:26 | <innovati> | sure? |
| 23:27 | <MikeSmith> | then I guess your code can check what interface the element has |
| 23:27 | <innovati> | is there a way to see all of the interfaces a browser has? |
| 23:27 | <innovati> | programmatically? |
| 23:29 | <MikeSmith> | I guess there would be, but not sure there’s anything exposed to do it conveniently |