htmx

so, in htmx it is fired on the new content

The alternative is to change the logic inside the `init` method to not expect <div id="main">

because you don't want to call it multiple times on #main

So, hence my clumsy question in the beginning ... how do you more or less replicate the `Intercooler.ready` way of doing things?

In the intercooler way, you would invoke the ready logic multiple times on the div#main DOM element

In the htmx way, it's the content, potentially inside the div#main DOM element

I don't think it should make a big difference, practically, but I am probably wrong

either way, you'd look up stuff inside the content to initialize with javascript or whatever

maybe share your code so I can look at it and realize that I've made a horrible mistake?

lol .... not it's not that bad... pretty sure it's just my specific implementation. In my `init` method, I essentially do lots of the equivalent of this:

```Intercooler.ready(function(rootContent) {
      rootContent.find("#my-element").click(function() { doSomethingOnClick() });
    });```

More or less yes, except that the `rootContent` in the htmx case is not the element whose innerHTML *is being swapped*, it IS the innerHTML element/content itself... which means that "find" finds nothing... cause it should be finding on the parent of that element

so `#my-element` is not in the new content?

or is `#my-element` the root of the new content?