Great ! It works now 😉 I will buy new glasses soon : I now see the description which explains exactly this inside the API reference 🙄 .

😎 I think I read somewhere that @User was going to make that more prominent / clearer. Either that, or I dreamt it! Or confused it with another topic 😂

I'll bet this was my issue earlier in the week as well.

In the past I used the post/redirect/get pattern. This means after submitting a form via http-post the server returned a 302-redirect response (if the data was valid). With htmx this is not needed any more. Nevertheless it was nice that I can check in tests easily if a post-request was successful (302) or not (200). With htmx this post/redirect/get dance is not needed any more. Great .... But nevertheless it would be nice to have different status codes: One for success (data from client was valid), one for error (data was not valid). Which http status codes would make sense? Freedom of choice is great, but guidelines help new comers.... Wouldn't it be nice to have small section about this in the docs? What do you think?

I am really hesitant to start claiming HTTP response codes

A hint like "if unsure use xyz" is really helpful if you are new to a topic.

yes, agreed

I'm trying to use hx-get within a Vue component in a Django template. The links load with the correct hx-get url from Vue when inspecting element, but when I click on the text, nothing happens. My code is as follows:

html
<div id="search">
<input class="form-control" type="text" placeholder="Search" aria-label="Search" v-model="search">
<p v-for="movie in movie_results"><a :hx-get="'/movies/m/' + movie.uuid" hx-push-url="true" hx-target="#content" hx-swap="innerHTML">[[movie.name]]</a></p>
</div>

javascript
window.onload = function () {
  var vm = new Vue({
    delimiters: ['[[', ']]'],
    el: '#search',
    data: {
      movie_results: [],
      search: '',
    },
    watch: {
       search: function () {
          this.searchMethod();
        }
    },
    methods: {
      searchMethod: function () {
        let ref = this;
        fetch(`/api_url/?q=${ref.search}`)
          .then(function (response) {
            response.json().then(
              function (r) {
                 ref.movie_results = r['movies'];
               }
             )
           })
           .catch(function (error) {
              console.log(error);
            });
       },
    },
  })
}

Thanks for any help!

you probably need to call

htmx.process()

on the newly added content: https://htmx.org/api/#process

I proposed https://github.com/bigskysoftware/htmx/pull/626 to handle error. But logic stays server server side anyway

I'll take it... My most complex page in this app I'm converting.

(That performance would be 100 if I wasn't pulling the Material Icons web font...)

I will review this change soon promise

Is there a downside to applying hx-boost on the body tag?

Also what's the point of https://htmx.org/extensions/morphdom-swap/ - I remember back in the ember days morphdom being touted for speed

Is that a speed up or a backwards compatibility thing at this point?

Not really, as long as the boosting behavior is what you want

The morphdom swap is a sophisticated DOM merge, so it does a better job of maintaining DOM state than the normal swap mechanism.

the normal swap mechanism is pretty good in most cases though

is there a way to disable it on a per link basis if something is causing issues? something like hx-disable-boost?

so probably ignore morphdom for the general case

hx-boost="false"

ah cool

duh obviously 🙂

yeah, I think morphdom is useful for some situations, but most folks won't need it

What do users of Livewire, LiveView, Sockpuppet, and other backend frameworks think about this chart? Does HTMX replace the functionality of these backend HTML-over-the-wire frameworks? What are the pros and cons of using HTMX vs one of these HTML-over-the-wire frameworks? Obviously, HTMX is language agnostic which is great, but besides that does it make sense to always go for HTMX? Let's say I'm a PHP dev, would it be better to use HTMX or Livewire in your opinion? What are the tradeoffs?

no rush 🐼

I don't think that's a good comparison. htmx takes a very different approach than LiveView-like frameworks. You can think of htmx as a server-side-agnostic extension of html, LiveView-like frameworks on the other hand are trying to blur the line between server and client (i.e. by bringing events and client-side state to the server side). Also, LiveWire kind of pretends to be LiveView-like, but it's very different due to the stateless nature of PHP. Why should you go with htmx instead of them? Well, it's much closer to the original web roots, there's much less coupling, which (in the long term) makes things more reliable.

Is there a way to update attributes instead of swapping elements?

Not really. If you put an ID on an element it should act kind of like that, but a new dom element will be inserted