htmx

If htmx supported HX-Reselect, I could implement this using:
```javascript
    res.setHeader('HX-Retarget', '#neg-count')
    res.setHeader('HX-Reselect', '#neg-count')
    res.setHeader('HX-Reswap', 'outerHTML')
```

Handled. They had no other messages on the server

hx-push-urlPartial vs Full Page Rendering

swapping a partial in every 2 seconds which is a div containing a table and the div has a y overflow + hidden so that the div is a consistent size the table has a scrollbar if it exceeds that size. I'd like to preserve the scroll position of the table after the swap. anyone ever done something like this? seems there is nothing available in HTMX to track this so I assume I'll need a bit of JS. I have done this before for the document (in asp.net webforms) but not on just a table element scroll position.. something like the scrollTop attribute of the TBODY child of the Table I assume, just not getting it right away here..

you could trigger an event with this content

If you target the innerHTML of the DIV, it should preserve scroll state I believe

hmm. the div is part of the UI swap (it is the content of a dashboard widget wrapper) but I will look into testing swapping just the table as innerHTML and see how that goes. as always, thank you for the quick reply!

no prob, yeah, if you can target the inside content it should preserve the scroll state

no idea why it was submitted or got a bunch of votes, but here we are

https://tenor.com/view/we-did-it-gif-6236810

maybe what htmx needs next is a call for blog posts about people's experiences using htmx. from that thread it seems like there are plenty of people using it in interesting use-cases, but their experiences aren't posted anywhere

\> 10 positive comments
\> 12 reasonable questions
\> 2 negative comments

finishing up https://www.youtube.com/watch?v=LRrrxQXWdhI … "corse grained hypermedia interaction" is one of these 'ah ha' perspectives

Because what are 90%+ of web apps other than manipulating form input data. Really basic HTTP 1.1 stuff. This is "coarse grained hypermedia interaction," to me… you're just typing and clicking forms. Why have the most swiss-army framework on top of any of this?

Of course this implies a "fine grained hypermedia interaction," which I couldn't exactly pinpoint, but a "fine grained user experience" is anything that might be more of an "instrument" where you play the notes and chords in the right order to produce a novel outcome. 

So from the beginning of a project, how novel is the thing we are making, and does it need anything more than coarse grained handling?

yes, most web applications can get away w/ coarse grained hypermedia exchanges.   htmx scopes down exactly how coarse grained the payload is, but it will still suffer if your application is chatty with the back end, in which case another approach might be better.  there is also idiomorph, a DOM morphing library that I'm working on, that might help make coarse grained hypermedia exchanges a better end user experience

i feel bad that you're writing all this javascript so that the rest of us dont have to

🙂 I wrote it so *I* don't have to write it

i dont fully have my head wrapped around "this is a hypermedia interaction" vs not, other than google maps and other high fidelity web apps, but i could see spotify web ui done in htmx, for example

so that's next. i know where to find the essays to read 😉

1000 users updating a room simultaneously?