Can I do this within htmx? Or would I have to write a JS function with ondocumentready ...

You could do it in the same function, just need

var table = cell.closest("table")

then

htmx.process(table)

hm .... but I do not have a real "table" - just a collection of rows/divs ... would something like wrapping a div around the whole construct with an id work? And then

var updateID = cell.closest("#wholeconstructid"); htmx.process(updateID);

var table = cell.closest("#table")

then

htmx.process(table)

Or you could make another wrapper like you said. Again, totally not sure this is going to work so I am hoping I'm not wasting your time.

more than happy to give it a shot. Maybe @User has another idea?

He would have answered already if he was available 🙂

Oh no I'm going to get a channel for myself, but I think I'm going to make a new HTMX app with node or deno, because the idea of sharing templates with the server and the frontend (for some features down the line that don't require a server request every time) is really appealing

sorry folks, super busy

looking at the logic:

js
      function handlePreservedElements(fragment) {
            forEach(findAll(fragment, '[hx-preserve], [data-hx-preserve]'), function (preservedElt) {
                var id = getAttributeValue(preservedElt, "id");
                var oldElt = getDocument().getElementById(id);
                if (oldElt != null) {
                    preservedElt.parentNode.replaceChild(oldElt, preservedElt);
                }
            });
        }

i don't see why you'd need to call .prcess on it.

I would link to the raw source on github: https://raw.githubusercontent.com/bigskysoftware/htmx/d869f80e78d512420d23e0356f8bafa77d5f9976/src/htmx.js

and then set a break point in Chrome on that

var id

line and see what is happening

maybe run the

findAll

in the console

sorry, really hard to tell from here

😑

hm maybe I can cook up a fiddle to test it.

Is there another method to achieve the same thing without using hx-preserve?

possibly, I have to admit I'm not sure I completely understand. Can you try summarizing again for me?

@User has inspired me to tinker with a pure htmx version of Wordle. Because why not? 😄 😆

Is it possible to change

hx-post

at runtime? I am updating it but it is always using what it was initially.

Currently, no. Not directly. If you change any of the hx- values, you’ll need to manually call htmx.process() before htmx will recognize the new values.

This is a long-standing request, though, and I suspect some day in the future this will update automatically.

Is

htmx

globally accessible?

I am trying the following but it still doesn't update:

javascript
      function processModal(selector, is_modal) {
        const el = document.querySelector(selector);
        if (el && is_modal) {
          let is_processed = el.dataset.processed;
          if (!is_processed) {
            let post = el.getAttribute('hx-post');
            let path = location.pathname;
            let url = `${post}?redirect_url='${path}'`;
            el.setAttribute('hx-post', url);
            el.dataset.processed = true;
            htmx.process(el);
          }
        }
      }

I am trying to do this by passing in a selector to the

htmx.process

function.

I tried it by passing in the element to the Form but it still doesn't work....

Is there a trick to get

htmx.process

to work correctly?

I’m not sure about the rest of your code, but the switch in

el.dataset.processed

looks sus to me. If htmx already thinks the value has been processed, then this won’t work to “reprocess” the DOM inside. Try removing this bit and see if you get better results?

Worst case - processing the same html twice - isn’t going to cost you much at all even if you’re wrong.

I removed the dataset logic. It still doesn't work. In my case I am using the same logic for both parent and modal forms which is why I don't want them to be evaluated multiple times. I highly doubt HTMX would be adversely affected by any

data-

attribute.