Ben Pate

Hi @sirinath, I've spent a little time on this, and have made some progress. But I'm not sure that this is complete. First, check out my PR #169, and tell...

A Side Note about Updating Nodes I re-read parts of your earlier note, and I think you're mixing in a lot of things, here. It is super-cool to be able...

Your "indexed" idea is a good step in the right direction. After thinking about it overnight, I think we can give the server even more control over page structures, and...

Hey @sirinath -- It's rare that I'm the one making things too complicated :) I think I'm following your code. However, I'm not sure how the "prefetch" would actually function...

Hi @clarkevans -- Yes. This proposal would align perfectly with what you're saying. I'm just using "records" as the unit of measure, but many cases would measure by "pages" instead....

I understand how a set of values could be sent to the server, and how you might use swap-oob to push a new set of values back to the client....

This is what I proposed yesterday (https://github.com/bigskysoftware/htmx/issues/130#issuecomment-677694208) with the exception of listening to “magic” IDs of “prev” and “next” instead of attributes labeled specifically for this job “hx-prev” and “hx-next”...

Howdy @clarkevans :) You're right on track, with one small exception. ### Listening to Scroll Events, not Triggering Them The way I'm proposing infinite scrolling, HTMX would handle all of...

FWIW, my demo site finally works. Check out http://sseplaceholder.openfollow.org as an example of the SSE and Pagination experiments I'm doing. When I get close to a real solution for infinite...

One more thought on this -- [RFC5998](https://tools.ietf.org/html/rfc5988#section-5.5) details using `Link:` headers to specify relationships between documents (or possibly fragments, in our case). This is separate from the `` tags that...