| 02:56 | <annevk> | I guess whatwg/meta should link that |
| 08:07 | <annevk> | smaug____: https://github.com/whatwg/dom/issues/685#issuecomment-419353747 |
| 09:20 | <smaug____> | annevk: how is legacy-pre-activation behavior related to clearTargetsTuple? |
| 09:20 | <smaug____> | I don't understand the discussion on the pr |
| 09:20 | <annevk> | smaug____: I changed where eventPhase is initialized |
| 09:21 | <annevk> | smaug____: rniwa pointed out you can observe eventPhase at that point through legacy-pre-activiation behavior and that it differs between browsers |
| 09:23 | <smaug____> | hmm, they dispatch change event at wrong time? |
| 09:34 | <annevk> | smaug____: re https://github.com/whatwg/dom/issues/685#issuecomment-419376808 the proposal is to always call capture listeners before bubble listeners, not just on hosts |
| 09:36 | <annevk> | smaug____: and no, they dispatch it at the same time, compare output of https://software.hixie.ch/utilities/js/live-dom-viewer/saved/6198 |
| 18:34 | <devsnek> | Domenic: finally finished this: https://github.com/whatwg/streams/pull/954 |
| 18:34 | <devsnek> | well not "finished" but... |
| 18:35 | <Domenic> | devsnek: sweet, I will look at it very soon |
| 18:43 | <zcorpan> | ...interesting http://software.hixie.ch/utilities/js/live-dom-viewer/saved/6203 |
| 18:47 | <devsnek> | i often use https://astexplorer.net/ |
| 18:47 | <devsnek> | it even has webidl |
| 18:48 | <zcorpan> | no browser does anything sane with that test |
| 18:56 | <Domenic> | devsnek: why did getIterator() disappear |
| 18:56 | <Domenic> | Oh what it's still on reader |
| 18:56 | <devsnek> | huh |
| 18:56 | <Domenic> | Wait no it's gone |
| 18:57 | <Domenic> | I was looking at the wrong tab |
| 18:57 | <devsnek> | do we still want the alias |
| 18:57 | <Domenic> | Yeah I think so |
| 19:03 | <devsnek> | Domenic: thanks for the quick review 👍 |
| 19:03 | <Domenic> | I try... I often fail, but this time I succeeded. |
| 19:19 | <devsnek> | Domenic: how do i unwrap the close promise |
| 19:25 | <devsnek> | the behaviour i think we want is `return ReadableStreamReaderGenericCancel(reader, value).then(ReadableStreamCreateReadResult)` but i don't know how to write that in spec |
| 19:30 | <Domenic> | devsnek: "Return the result of transforming ! ReadableStreamReaderGenericCancel(reader, value) by a fulfillment handler that returns ! ReadableStreamCreateReadResult(value, true, true)" |
| 19:30 | <devsnek> | prose ftw |
| 19:30 | <devsnek> | thanks |
| 19:30 | <Domenic> | "transforming" has a promises-guide pseudo-definition |
| 19:31 | <devsnek> | it would be cool if stuff like that was somehow linked |
| 19:31 | <devsnek> | like with the locks api earlier |
| 19:31 | <Domenic> | It is |
| 19:31 | <Domenic> | <a>transforming</a> |
| 19:46 | <zcorpan> | is "The rules for parsing tokens in foreign content" not an insertion mode? |
| 20:07 | <rniwa> | annevk, smaug____: I used to think event dispatching part of the spec was pretty clean.... not anymore :( |
| 20:08 | <smaug____> | it is very complicated |
| 20:08 | <rniwa> | annevk, smaug____: all sorts of craziness lurks in there. it's just not well spec'ed... |
| 20:08 | <smaug____> | thanks to shadow DOM |
| 20:08 | <smaug____> | it is reasonable well spec'ed but just hard to read |
| 20:08 | <rniwa> | smaug____: yeah... at least we don't have multiple-generations of shadow tree craze anymore |
| 20:08 | <smaug____> | yeah, that was super complicated |
| 20:09 | <rniwa> | smaug____: yeah, when each host has multiple generations of shadow roots with distribution happening in each |
| 20:09 | <rniwa> | smaug____: with shadow element |
| 20:09 | <rniwa> | smaug____: and then those things are nested |
| 20:09 | <rniwa> | smaug____: all bets are off as to comprehending what the heck is happening to an event being dispatched |