I’d look at it from the other direction: at one point we didn’t swap anything except the body.

I believe turbolinks does a more complete job of merging header info.

I'm just whining because I soooo want to use HTMX in my current project -- especially for things like hx-boost -- just getting that SPA like feeling without the 800 pounds of SPA. But not swapping the description tag won't work since SEO is super critical for this project.

I believe for SEO, the crawlers should just follow the links normally

I'll have to run that by the client -- thanks so much for your attentiveness

Seo and boost aren't related I think. My understanding is that each page is pulled separately and indexed in isolation

Thinking about SEO a bit more outside the context of

hx-boost

. If I want Google to follow natural links, that means I can't use just:

<a hx-get="my-other-page">Other</a>

. Would I have to do something like this:?

<a href="my-other-page" hx-get="my-other-page">other</a>

hmmm... It looks like I can use

href

instead of

hx-get

and it still works with

hx-target

, etc. That's very cool.

Hey there, I am still trying to figure out how far I can go with a server rendered approach. It seems pretty obvious to me that anything rather coarse grained is a very good fit for htmx but when it comes to rather fine grained components I am not sure or rather sure I wouldn’t work well or at all. Let’s say I have an input component for emails or an input component for a specific date format component where I want to check the format while I type and give immediate feedback/error messages on invalid input. I don’t see how this could work sending server requests. But even on a more coarse grained level I am having trouble to figure the best approach. Imagine a form that has 3 input components. And let’s say each distinct value within one component could change the behavior of the other 2 components . For example from enabled to disabled or suddenly to having an error message etc. this certainly would work with an SSR approach BUT I guess I would end up with lots and lots of server routes to build and maintain and also it might be to slow for something when done via DOM manipulation in mere microseconds to suddenly now take up to a few 100 milliseconds. What is the usual approach here that ppl take?

I think for things like you've described (e.g. forms enabling themselves based on other input) then people would reach for something like Alpine and do it on the client side. Otherwise you will end up with various routes for querying the server.

So moving the

hx-sse

to the

table

tag instead of the div seems to have helped. Seems to be working now. I'm not exactly sure what I did but 🤷‍♂️

Okay - so I tried to channel my inner @mysterious-toddler-20573 and replace SSE with some load polling. Works wonderfully save for the fact that my progress bar isn't being replaced. I'm returning the following while I'm getting results:

html
<progress max="100" hx-swap="outerHTML" hx-get="get-logs/?logs=12345" hx-trigger="load delay:1s"></progress>

The problem is that my final results html gets put as a child of the progress bar, rather than replacing it.

can anyone spot the obvious mistake?

le sigh - I think it's some weird caching. Hard refresh seems to have sorted it. Sorry for the noise.

Is it intended behavior when a form field is "disabled" that it will not pass it's value in the request?

there is no shame in client side scripting in these cases

i would bet that the input.value is coming back null, i don't recall us specifically excluding disabled inputs

it is coming back null

would verify the same behavior in vanillajs

I know that's not the behavior using vanilla js and ajax

I could be wrong though. It might be a select field specific thing

I know on input fields it's not the case

And in this specific case I'm trying a select field

that looks like it's working, lemme look at the htmx source

@mysterious-toddler-20573 It might be a select list thing. That's what I just tested it on

updated to use select, still working, lemme look at the source

😑