it'll happen with the transition api almost certainly.

yeah, thats chrome. is firefox adopting it?

hope so!

Just found out about HTMLX after my framework (Laravel) released fragments feature. Looks cool and time-saving

if I have this html:

html
<div hx-boost="true">
  <form onsubmit="event.preventDefault(); return false">
    <input type="submit">
  </form>
</div>

I shouldn't expect clicking the input to issue a boosted form submit should I?

maybe an event ordering issue

could it be a propagation issue?

I'm thinking that the

onsubmit

is called after htmx has already processed it and is sending the request.

I'm behind in my prs but I can try to put together a test next week during 🦃 time

We’re starting a project at work using PHP/Symfony, and my coworker came to me saying, “how about we try htmx?”. My regular seed planting over the past months is paying off. We’ll use twig templates + htmx as far as we can go, instead of resorting to an SPA by default on the frontend (when that happens we reach for SvelteKit). Quite excited to finally get to work with htmx on something real!

Damn, i should probably plant seeds

what did you do, brown bag talks or team meetings?

I am not sure how to start this convo

For one moment, I think my coworker even had the thought of porting an internal tool of ours to templates + htmx. It was coded with Node/Nest.JS on the backend and Sapper on the frontend in 2019-2020. So, that typical backend-API-frontend split. Today this tool has become obsolete because Sapper was replaced with SvelteKit in 2021, and then SvelteKit itself got a major and partially breaking upgrade this year. So we are effectively having to treat this not so old tool as legacy code, requiring careful planning to get it back on track with latest SvelteKit while not disrupting its internal use. It’s basically a CRUD app, though. I think we would have been in much less pain with a stable “full-stack” framework as a base and some htmx/Stimulus on top

We’re a small dev shop so we don’t really have brown bags; but I first mentioned htmx on our “craft” channel where we share dev tips and cool stuff. Later on I brought up the philosophy with hypermedia etc one day in the morning while having coffee. Then I showed the same coworker how there were multiple things happening preparing for a “post-SPA-by-default world”, with other approaches like Marko. The “essays” really helped as they show htmx is founded on solid theory. They also help because all the talking around htmx is consistent as a result, which is a strong communication asset. So anyways, I guess that triggered curiosity, and then it slowly built up? Also, as he was investigating recent developments about PHP/Symfony, eg the symfony-ux initiative (which is basically a Hotwire integration), he found an enthusiastic Symfony+htmx video tutorial — boom.

Looking for a way to programmatically prevent htmx from firing (anything) like hx-get from within a click handler. Similar to how

halt

works here? https://htmx.org/examples/edit-row/

This isn’t what you’re looking for is it? https://htmx.org/attributes/hx-disable/

https://htmx.org/extensions/disable-element/ ?

https://twitter.com/addyosmani/status/1592907811968626688?s=46&t=DM7C9sIREG1CHFPaEZfvEQ 🤩

This is going to change the game. I need to make an extension for it.

I agree, this is one of the few things that are only possible with client-side routing, and for some apps this is a requirement

feedback welcome before I publish generally

botched link

thx

is this meant to be "exposure"?

either way it's a slightly confusing sentence

replaced w/ an even more confusing reference