https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • e
    I think for boosted its the same no? The issue I'm gonna have next is I want to add new html to the page and their head tags appended and not to mess with what exists.
  • m
    yes
  • m
    I'm adding a directive, 
    hx-head
    that allows you to specify how to treat the head elements
  • m
    e.g.
    Copy code
    html
<head hx-head="append">
     <link rel="stylesheet" href="page-style.css">
</head>
    would append the link to the head if it didn't exist
  • m
    Copy code
    html
<head hx-head="append-always">
     <link rel="stylesheet" href="page-style.css">
</head>
    would append the link even if it already existed
  • m
    etc.
  • m
    people have also asked for the ability to re-execute a script
  • m
    it's a challenging problem for htmx, because you can both have full page boosted responses as well as partial bits of HTML, and so the behavior of the head tag isn't as straight forward as, for example, in turbolinks
  • m
    so I need to think (and help thinking) about it
  • e
    I think the calling element should determine how it should handle the head tags
  • e
    append-always may result in too much in there if it's always appending
  • e
    like boosting is like a anchor link page refresh it's different then a targeted append
  • e
    boosting should kind of be sync, targing should be append
  • m
    mmm
  • m
    should it be controlable w/ an attribute?
  • m
    to override the default
  • m
    I think I agree w/ the defaults: * boosted is sync * non-boosted is append (if absent)
  • m
    some other concepts I'm considering working in: 
    hx-head="sticky"
    this element will never be removed from the head
  • m
    hx-head="reexecute"
    this element will be re-executed/added on every request
  • m
    but then, on boosted pages, we probably always want to re-execute all the javascript
  • m
    😑
  • m
    I'm going to start a gist on this
  • b
    Slight change of topic...but should it be possible to make a delete request where the server answers a 204 - No Content. Here's example Ruby code:
    Copy code
    # View
# The parent element has these attributes: "hx-trigger" => "click", "hx-swap" => "outerHTML".
<%= link_to "Delete",
            task_path(task),
            class: "button button-decline",
            data: {"hx-target" => "closest .task", "hx-delete" => task_path(task)} %>
    Copy code
    # Controller Action
def destroy
  Task.find(params[:id]).destroy!
  head :no_content
end
    Does HTMX not respect 204 when swapping?
  • m
    204 means no content has been given by the server, so no swap occurs
  • m
    this is, unfortunately, an ambiguity in the the meaning of "No Content"
  • m
    we've argued about it a lot
  • b
    Oh, OK, so perhaps I shouldn't swap at all but completely remove the effected HTML element?
  • m
    one sec
  • g
    Just return 200
  • m
1...876877878...1146Latest