
Sign up to save your podcasts
Or


John says what's up with marketing for small businesses
Youtube: https://www.youtube.com/watch?v=S7BX2ocn7XM
Anthony's talk at Big Sky Dev Con:
https://www.youtube.com/watch?v=uVKSmR_hBMs&t=9142s
This episode on youtube (i.e. see faces)
https://www.youtube.com/watch?v=LQfKmpx7QZ8
Mentioned, how to submit and reset a form on success using htmx:
hx-target="#candidates_add_form"This assumes the last row is the add form, and places the newly added item directly above it.
"We've done them all now"
All headers grouped
===========> REQUEST HEADERS
======> Flags
*HX-Boosted - was it a boosted link
*HX-Request - is it an htmx request
*HX-History-Restore-Request - is it a back button restore request
======> Auto-sent variables
*HX-Current-URL - current url page is at
*HX-Target - id of target if has id
*HX-Trigger-Name - which element triggered it by name
*HX-Trigger - which element triggered it
======> User Variables
*HX-Prompt - user is asked to provide prompt, this is what they typed
============> RESPONSE HEADERS
======> Browser & history commands
*HX-Location - hx-boost reload to page
*HX-Redirect - regular redirect
*HX-Refresh - refresh page
*HX-Push-Url - push url to top bar
*HX-Replace-Url - replace url in top bar
======> override attributes
*HX-Reswap - sets hx-swap value
*HX-Retarget - set hx-target value
*HX-Reselect - set hx-select value
======> Trigger events
*HX-Trigger - trigger an event on client immediately
*HX-Trigger-After-Swap - trigger an event after swapping in html
*HX-Trigger-After-Settle - trigger an event next lifecycle
i went to #BSDC2024 (not an htmx con) so you don't have to.
here's my own recap of all the talks
Every talk is available to watch at: https://bigskydevcon.com
Use this response header to send event trigers to ANY client side browser event (javascript, htmx, custom, etc)
HX-Trigger - as soon as response received
HX-Trigger-After-Swap - after new html is swapped in
HX-Trigger-After-Settle - after new html is settled and processed by browser
This episode explores what an optimistic ui might look like in htmx. Also: is it what we want to do? Is it even possible? Or is it incompatible with the idea of having the dom as the true application state?
Original tweet:
https://x.com/noahflk/status/1795758603577545035
DHH responses:
https://x.com/dhh/status/1796163806650868149
Htmx guy responses:
https://x.com/htmx_org/status/1796182554883539236
From the publisher's feed