I've said it before, but HTMX is really such a breath of fresh air. Django came to popularity at a time when server-side was the norm. In the past several years there has been so many SPA & JS frontend frameworks and tools and options that I think it really throws newbies to Django for a loop, and makes older django folks feel like they've got to figure a bunch of new stuff out. There's no 'standard' approach to the front end other than the built-in templating, and lots of people have felt that that approach was outdated. HTMX lets us stick to what django is good at - server-side stuff, mainly - without feeling like we're losing out on the modern world. It kind of brings the django project back full circle to its origins, but with the power of the best parts of 2021 web technology.

Not sure if this is a bug: but if you set as part of a response with hx-push-url+hx-get or hx-boost (so document.title is set) and hit the back button, the original head is not reset.

that's a bug

It seems hx-boost with a form using GET does not push the new URL (using hx-get+hx-push-url does).

btw is anyone using htmx with npm? Or does everyone just use the CDN?

Dear @User , thank you for helping. We also use SameSite=STRICT, but we decide to implement CSRF also. FYI: https://portswigger.net/web-security/csrf/samesite-cookies

Go ahead, I don't plan to submit a talk for DjangoCon US.

Nice and short article about CSRF. It strengthens my opinion that CSRF tokens are not needed for my current context.

Yep, django docs get into detail on when CSRF is needed and why: "It deliberately ignores GET requests (and other requests that are defined as ‘safe’ by RFC 7231#section-4.2.1). These requests ought never to have any potentially dangerous side effects, and so a CSRF attack with a GET request ought to be harmless. RFC 7231#section-4.2.1 defines POST, PUT, and DELETE as ‘unsafe’, and all other methods are also assumed to be unsafe, for maximum protection."

"It" being the CSRF middleware

Hello everyone ^.^

I'm trying to make a quiz with htmx -- multiple choice quiz. I want to show four buttons, each one option, and send the choice to the server, which checks if it is right, and sends back a "correct" and a next quiz, or an "incorrect" ... i am having a hard time learning the very basics. i am looking at the example pages and they are cool, but i don't know what the necessary components are or the naming structure. any pointers appreciated

i'm reading this now and it is helpful: https://dev.to/libsyz/learning-ajax-made-easy-build-an-app-with-htmx-gie

Hi @User sounds like you want the buttons to have an hx-get attribute on them, and then maybe target the div that is surrounding the quiz with the hx-target attribute. You would probably want to include the answer chosen using the hx-vals attribute on each button.

@mysterious-toddler-20573 thank you 😄 that is helpful. I will do some more docs reading

Amazing. I got a basic POST working to replace the text... now on to more sophisticated transformations ^.^

🙂 It's not too hard once you get the hang of it 👍

How can I make 4 buttons that send 4 different sets of data?

does it make sense to have 4 separate s ?

sure, why not?

I would use a hx-vals attribute on each button to send different values with each

does

hx-vals

have to be json?

😄 thanks for your help =] i think i have most of it figured out now

great to hear!

I have the gut feeling that it makes more sense if people as questions at stackoverflow, and not here. I guess most people google before asking. Answers at stackoverflow can be found easily. What do you think?

It makes sense but when u find it handy here to also get a detailed answered if anyone is interested in answering you is also great

Looking at SPAs created with Angular/React I think it would be faster, if they would use htmx. Up to now it is just a vague guess. It would be really cool if you could measure it. Has someone ideas here?