probably right

😑

yeah this would not fix the alpine case

because the specific element that holds the state would be dsetroyed

although potentially alpine morph might be smarter for that specific case? idk how that works + if the cache grabs the info alpine would need to restore correctly

I'm seeing something funky, and wondering where it is. On a site where I'm using htmx targeting the body with a boost, I'm trying to link to an anchor on another page. However, the click seems to be losing the fragment. To see it in action, look at https://bitbadger.solutions/open-source/myweblog/installing.html and scroll to the "Other Configuration" heading under "Environment". The text "the advanced configuration section" should go to an anchor in the target page; if you hover over it, you can see that that's where it should go. When you click, though, you go to the top of the page. (Interestingly, if you hit "back" at that point, it will go back to the previous page with the fragment that was missing from the navigation.) Any thoughts?

if you open chrome dev tools and run

var filename = location.pathname.match(/[^\/]+$/)[0]

does that crash anyone else's tab?

no only in one tab??

wierd

I got vite based html auto reloading working:

plugins: [
    {
      name: 'watch-external', // https://stackoverflow.com/questions/63373804/rollup-watch-include-directory/63548394#63548394
      async buildStart(){
        const htmls = await fg(['**/*.html']);
        for(let file of htmls){
          this.addWatchFile(file);
        }

        const jinjas = await fg(['**/*.jinja']);
        for(let file of jinjas){
          this.addWatchFile(file);
        }
      }
    },
    {
      name: 'reloadHtml',
      handleHotUpdate({ file, server }) {
        if (file.endsWith('.html') || file.endsWith('.jinja') ){
          server.ws.send({
            type: 'custom',
            event: 'template-hmr',
            path: '*',
          });
        }
      },
    }
  ],

and then in my entry point:

js
if (import.meta.hot) {
  import.meta.hot.on("template-hmr", (data) => {
    const dest = document.location.href;
    htmx.ajax("GET", dest, { target: "body", swap: "nanomorph" });
  });
}

Nanomorph doesn't preserve form values in swap though

will look at this tonight

I think the morphdom extension is wrong - I get errors when I try to use it as is, I need to change it to remove the outerHTML similar to the nanomorph api

bleh morphdom also blows out the form input

erp

I have only recently discovered HTMX and its was a breath of fresh air. We'd already written some custom HTML over the wire components but they have all been replaced with HTMX as of 20 hours ago in production.

Thanks for the package.

Is there a way to unboost ?

hx-boost=false

nanomorph CLAIMS they keep the form values between swaps: https://github.com/choojs/nanomorph/issues/19

no, I don't think they do

I think I have to get my server to populate the value attribute and then they'll update the form to use the new value

it says they "copy input values", i.e. from the incoming node, which they do

yeah uses server values over current values

probably desirable in a spa context where the canonical value of the form will be tracked in a variable

yeah

@hundreds-camera-24900 your next assignment is to big brain on the nano morph code and think about a “merge” swap for extension based on it but tuned for htmx, to be folded in for htmx 2.0