Going with this approach. Running into https://github.com/bigskysoftware/htmx/issues/523 now though. I swear there was a way to keep the focus of an input element, someone mentioned it on Discord recently

Yes there is. Just use the HTML autofocus attribute.

perfect 😄

I haven’t tried it, but you might also see if the morphdom plugin helps address this. It does a more sophisticated swap which is supposed to preserve DOM state better.

I’ll volunteer to make this one the background image of every page, if you’ll let me.

The other thing I had a question about was showing a loading icon with hx-ws - is there support for the htmx-indicator stuff? Not sure if that even makes sense for websockets though

No, there’s no support for hx-indicator.

Since the server pushes messages to the browser, we really don’t have a “loading” state to work with. But, you could fake it outside of htmx by just adding a little spinner whenever you need it.

Yeah I'm starting to feel like maybe I should use hyperscript if I have all these complicated rules/requirements

Yes. You should definitely check it out. Hyperscript is weird and beautiful and 10x simpler than JavaScript. I came here for the htmx, but stayed for the hyperscript.

Sorry for jumping in.... but, since this is related to the site... would it be possible to have the site's navigation bar fixed to the top? This is specially notorious for me in the docs page. It is a super long page (in my browser it says it is over 28000 pixels tall!). So, when one is at the bottom, scrolling back to the top gets very old quickly. I'm often reading those docs, so this could make things a little easier. My laptop doesn't have a 'home' button, so, that's not an option for me. Not sure how hard is to add the CSS, but the styles themselves are quite simple. For the media query over 720px:

.top-nav{ // in addition to the current properties
  background: #fff;
  -webkit-position: sticky;
  position: sticky;
  top: 0px;
  z-index: 2;
}

of course, please submit a pull request

Great, will do.

java developer asking about SSR, and a comment by @User that could use some upvote love: https://www.reddit.com/r/java/comments/qme8ai/java_ssr_web_ui/

Done

Nowadays people are really over engineering web projects

My feedback after using both HTMX and hyperscript in small projects: It's not quite clear when I should use one over the other, and how I can make them integrate well. For example, I've found myself starting with HTMX, realizing I need more advanced behavior, and then "switching" to hyperscript.

that sounds like about the right workflow

Sometimes I'll start with hyperscript, realize I'm over engineering, and then switch to HTMX though

htmx should be used for communicating w/ the server, hyperscript for more pure front-end interactions

I'd like it if both of their websocket modules played nice with each other though - like if I could have hyperscript use the websocket connection from hx-ws somehow, rather than having to rewrite and switch all in to hyperscript (which adds complexity as well).

heck just rewrite it in hyperscript

absolutely

this is absolutely the long term goal

I realize I'm "complaining" about two experimental projects not working together now that I think about it lol

not at all, they should work together, that's the goal

Yeah, about that…

We’re in the middle of reworking the htmx support for WebSockets right now. I like hyperscript’s support better, actually, because it makes a “proxy” object that can survive disconnects more easily.

Each needs its own implementation, though, because htmx needs to work without hyperscript. But once we have moved htmx WebSockets into their own separate extension it should be easier to iterate it independently and add a deeper connection to hyperscript.

For instance, if hyperscript is available then htmx might just use the hyperscript implementation directly.