[www.google.com](https://denizaksimsek.com)

# asd ## asd ### asd #### asd ##### asd ###### asd

lmao the ammount of rickrolls that will be done in the following days.

with custom links

imagine a guy comes here, clicks a wiki link just to get rickrolled

no fun allowed!

# ||get jumpscared||

How do I disable scrolling when new content is appended to page via HTMX? I just have

hx-swap="outerHTML"

is it worth to get htmx and hyperscript as npm packages, webpack them into a bundle and ship it with the bundle?

cuz htmx + hyperscript is 150kb, wonder if it would be possible to strip those packages to only the modules/functions that are used in the code

I was looking over that earlier, problem is I don't want it to scroll, but it seems like it's doing that even though I'm not asking it to. There's no parent elements with scrolling enabled (the navbar has it, but that's not a direct parent), so I'm not sure

Isn’t the V-for-vendetta character causing chaos by fighting the establishment?

How about Wreck It Ralph?

I'm returning an HTML fragment (loaded by HTMX) from the server that looks like this:

<h1 hx-on="htmx:afterSettle: alert('hello1');
           click: alert('hello2');">Hello</h1>

I'd like an alert to be shown as soon as the HTML returned in the fragment is loaded. But nothing happens. Clicking on the header will show an alert with "hello2". I've also tried changing the event to

htmx:afterSwap

to no avail. How can I make this work?

use

htmx:load

event

Thank you, that works!

I have this piece of html:

<div id="showIt"><!-- --></div>

<sl-button
        id="someId"
        variant="primary"
        style="margin-bottom: 1rem;"
        hx-get="/my-app/stuff"
        hx-target="#showIt">
    Show it
</sl-button>

/my-app/stuff

returns this HTML:

<button hx-on="click: alert('ikk')">Close</button>

This works exactly like I want the first time I click on the (sl-)button with id

someId

. But the second time, I essentially just want the second button to be re-rendered again. But instead, I see two buttons next to each other with the text "Close" and I get an with HTMX:

mx.min.js:1 htmx:swapError
`

and

TypeError: t.onHandlers is not iterable

I don't understand why, and using

htmx.logAll()

doesn't make me any wiser.

can reproduce, looks like a bug in hx-on implementation

Thank you, should I report it on github?

yep

I think there it should've been

for ... in

, not

for ... of

, -> https://github.com/bigskysoftware/htmx/blob/master/src/htmx.js#L924

oof

my bad

If I have a page with many HTMX loaded elements, some of them have actions like:

hx-trigger="load, every 30s"

I can make everything inside a tag "stay" with using

hx-preserve="true"

on parent elements. I now want to start a js library (a chart that is being drawn) when htmx swapped in the

<div>

to hold the chart. I tried:

htmx.onLoad(function(elt) {
  chart();
}

but this initializes

chart()

everytime another

load, every Ns

triggers a reload. is there a way to identify a specific element for

onLoad

?

check the value of elt argument, it should contain the loaded element, so you can only initialize what is needed

Hi everyone, I am trying to use htmx to load some elements after a vanilla (no htmx) POST form submission. My htmx elements are using the

hx-trigger="load delay:1s"

pattern and work fine before the form submission, but stop after the form submission. The desired behavior is to have the elements to continue to be triggered while the form submission is in flight. I have tried using

hx-sync="#myform:queue first"

, but as described in the docs queues the events to be triggered after the form submission returns. Is there any way that I can have the elements trigger while the form submission is in flight? Thanks!

yes, what @ripe-action-67367 said (as usual). You want to look for chart elements within

elt

rather than globally

Vanilla form submissions are handled by the browser and cause full page refresh, which among other things will unload running JS. I'm not sure about exact timings when this happens, but if I understand your case correctly, this can't be fixed by htmx

can you link to this issue, I'll fix it today 😑