05:48
<jjaschke>
Following up on that — what is the expected behavior for a maplike (or setlike)? In my understanding, a maplike should work as a map, so iterating should use live data.
But then there is this wpt, which (given the commit message) deliberately iterates on a copy of the data. Is there some section in the spec I’m missing, or is this not defined properly?
07:34
<Ms2ger>
I think the latter
08:51
<jub0bs>
freddy: Sorry for dropping the ball on this! I'll send you an email now.
08:59
<Domenic>
maplike and setlike being undefined is the major motivation for that in-progress PR.
10:18
<jub0bs>
* freddy: No problem! Thanks. I'll shoot you an email on Thursday.
10:19
<jub0bs>
freddy: Done 😇
16:07
<chargeitall>
The button background color is not changing when toggling between fullscreen and no fullscreen using F11 and Esc. Link: https://pastebin.com/KQqMMjUh
16:59
<Dan Fabulich>
I have a random shot-in-the-dark question… not sure if this is the right place to ask it. Recently HTMX has seen a surge in popularity, and, in particular, I think its users have some interest in standardizing some of its features, especially having HTML have the ability to do same-origin requests for HTML document fragments and swapping/merging them into the current page. Is WHATWG the right forum to discuss something like this? (If not, is there a better place for that discussion?)
17:03
<zcorpan>
Dan Fabulich: it seems like a good place to discuss. File a spec issue for html
17:15
<annevk>
There's probably an issue for client-side includes already, if I understand the suggestion correctly.
17:16
<Noam Rosenthal>
not exactly, it's submitting a form that only replaces part of the document
17:17
<annevk>
Oh I see. Declarative AJAX.
17:39
<Dan Fabulich>
I'm actually a bit stumped on how to write "use cases" for declarative AJAX. (It does so much!)
18:10
<Noam Rosenthal>
Dan Fabulich: search the web for "HTMx use cases" and you'll probably find copy-pastable things
18:10
<Noam Rosenthal>
(An HTMx fan here)