| 13:54 | <Ms2ger> | Quick pop quiz: |
| 13:54 | <Ms2ger> | var element = document.createElement("div"); |
| 13:54 | <Ms2ger> | element.setAttribute("data-1", "value"); |
| 13:54 | <Ms2ger> | var propdesc = Object.getOwnPropertyDescriptor(element.dataset, 1); |
| 13:54 | <Ms2ger> | What is propdesc.value? |
| 13:55 | <ondras> | "value"? :) |
| 13:55 | <Ms2ger> | Good guess, unless you're Chrome |
| 13:55 | <Ms2ger> | Any ideas what Chrome does? |
| 13:56 | <ondras> | hm, tried it, weird. |
| 13:56 | <ondras> | looks like a bug to me |
| 13:57 | <Ms2ger> | Agreed |
| 14:58 | <domfarolino> | Have you filed a bug? (Am interested in CC’ing myself) |
| 15:00 | <Ms2ger> | Not yet |
| 15:28 | <Domenic> | annevk: I think we can use infra queues; did you see any hard blockers? |
| 15:30 | <annevk> | Domenic: well, the oldest task thing that skips over stuff that are currently not active |
| 15:31 | <annevk> | Domenic: that's a little different from dequeuing |
| 15:31 | <Domenic> | Oh, right, I was thinking you could just look at queue[0], but you might need to actually remove queue[1]. Nevermind. |
| 15:31 | <annevk> | Domenic: oh, if you rewrite as a loop, also account for there not being a task |
| 15:32 | <annevk> | Domenic: I didn't do that I think |
| 15:32 | <Domenic> | Yeah, algorithmizing it will involve a decent number more steps. Probably for the best, although I'm a bit worried about any "step 1" references. |
| 16:42 | <annevk> | Ah yeah, "step 1" is terrible |
| 16:42 | <annevk> | A fair number of those also doesn't have an xref |
| 16:47 | <annevk> | Domenic: I guess microtask was always a queue, but that does assume there cannot be both active and non-active microtasks queued, which is usually reasonable, but nested event loops make it not so? |
| 16:48 | <annevk> | Domenic: maybe even then, ugh, this is hard |
| 16:48 | <annevk> | I think it's probably fine |
| 16:57 | <Domenic> | annevk: from what I can tell (and I updated the PR to clarify) microtasks don't care about if their document is fully active or not, unless they get moved to become real tasks by spin-the-event-loop |
| 16:57 | <Domenic> | That said, I think bz and some Chrome folks are discussing changing that in a contemporary issue |
| 16:57 | <Domenic> | Not sure if that's what you mean by "active and non-active microtasks" |
| 16:59 | <annevk> | Domenic: oh, Job microtasks use "check if we can run script" so it's actually happening at a lower-level |
| 16:59 | <Domenic> | Ahh |
| 16:59 | <Domenic> | That's a bit strange |
| 16:59 | <annevk> | Domenic: not sure if that's correct though |
| 16:59 | <Domenic> | Yeah, when we figure out those contemporary threads we can maybe fix that too. |
| 17:58 | <Domenic> | #lazyweb any specs that use [Exposed] on members for something that's exposed to multiple globals? I.e. only a subset of members are in each global |
| 19:22 | <TabAtkins> | Domenic: https://drafts.css-houdini.org/css-typed-om/#stylevalue-objects |
| 19:22 | <TabAtkins> | The parsing methods (which invoke the CSS parser, not thread-safe in all UAs) are restricted to Window, but the class itself is availble to workers too |
| 19:57 | <annevk> | Domenic: xhr |
| 20:04 | <Domenic> | Thank you! |