I'm having some issues getting loading states to work. This is my body tag:

And the form which is displayed in a modal (I've also tested adding the extension to the form tag)

The "Confirm" button is not disabled on submission

I can't see what is wrong here

Hey everyone.. First post here.. I was after some best practice advice for pushing URLs on post/put/delete.. is it generally preferred to do them in the markup with

"hx-push-url"

or on the server with a

"HX-Push"

header? TIA

Maybe you are right and it is only an issue when it relates to accepting user generated input. Javascript isn't my strength and I don't know the answers, but I definitely need this community to advise me (and other newer front-end devs) on what the best security practices are for this new tech. After initial load of extensions, are any additional extensions that are loaded into the browser later (by whatever means) automatically accepted by htmx? what if an extension is compromised or malicious? what are the consequences? these are all just questions which I think should be considered at some point. I guess what I mean is that "boundary" doesn't necessarily just mean performing ajax calls. Or maybe it does and that is the line htmx wishes to draw (which is fine). Just as long as everyone is on the same page that if you or your clients want any security beyond that then you have to take those steps yourself or just ensure you are following all those other security best-practices suggested above.

There's no such thing as security on the client-side. Once you send your html/javascript/etc, the client is free to do with it as they please. Extensions won't just load themselves, either you send them, and that's your problem, or something else on the client loads them, and that's not your problem.

Does hx-vals=“unset” work? It’s throwing a syntax error. ‘{“unset”: “true”}’ or similar prevents the error but doesn’t actually unset the inherited vals

@most-jelly-15242 👆

looks like a bug, you can use

hx-params

to filter everything out

hey guys, i've raised a Q on twitter on the placement of hx-ext="client-side-templates", my HTML: Current Running Task Progress <div hx-get="/tasks/{{ data.job.id }}" hx-trigger="every 1s" hx-target="#task_output" nunjucks-template="job_rq_template"> {{ items }}

i'm monitoring RQ worker job process (polling every min) the response is in JSON and i'd like to parse it using the template

any error messages?

The extension is really simple, so it should be easy to debug

iirc, there may be some API changes that affect it

no, if I have hx-ext="client-side-templates" anywhere in my DIV's I don't see any response from hx-get request

in nunjucks

huh

do you see the request in the dev console?

here is the response I get before I add client-side-templates: { "items": { "task_creation_time": "Wed, 29 Jun 2022 13:37:08 GMT", "task_end_time": null, "task_id": "0f527518-4809-4d3b-ae8e-874722c3dd26", "task_progress": {}, "task_result": null, "task_start_time": "Wed, 29 Jun 2022 13:37:08 GMT", "task_status": "started" }, "status": "success" }

this is the sum total of the extension, not very much!

i don't see how it's possible the extension could break requests

and yet here we are

grug grim smile

question is which DIV do i add: hx-ext="client-side-templates" 🙂

as adding it makes "task_output" disapear (hx-target)

it should be added on a parent element, and then you place the

nunjucks-template

attribute on the element that issues the request

let me put together a codepen

here is my code for reference 😉 Current Running Task Progress <div hx-get="/tasks/{{ data.job.id }}" hx-trigger="every 1s" hx-target="#task_output" nunjucks-template="job_rq_template"> {{ items }}