https://htmx.org logo
Powered by
# htmx-general
  • e
    I’m working on a Haskell + htmx example app and need to decide on how to do user authentication. The routing framework I’m using has support for basic user authentication. Is basic user authentication a good fit for htmx apps? I only have experience with JWT based authentication which doesn’t seem to be a good fit for htmx apps
  • m
    JWT doesn't make much sense for htmx. Ideally there is a traditional auth framework that uses session cookies for your platform.
  • m
    basic user auth (like HTTP Auth) is typically not what you want
  • p
    Hey
  • p
    How can i remove the space where my spinner is while its not showing?
  • p
    Click Me!
  • p
    https://htmx.org/docs/#indicators Im using this code, works perfectly but while its not showing the spinner, it looks a bit ugly
  • b
    Definitely go for cookies if you can. Avoid Basic auth unless you can guarantee https and that users aren’t using their credentials anywhere else. (Even then avoid it as you’ll fail any security audit.) JWTs are more trouble than they’re worth.
  • m
    In the same doc page you referenced there is an explanation about adding additional CSS classes if you want to hide the element | While the htmx-indicator class uses opacity to hide and show the progress indicator, if you would prefer another mechanism you can create your own CSS transition like so:
    Copy code
    css
    .htmx-indicator{
        display:none;
    }
    .htmx-request .my-indicator{
        display:inline;
    }
    .htmx-request.my-indicator{
        display:inline;
    }
  • p
    Hey, yes i had that CSS already on my page and space is still showing not sure why
  • p
    I have also added style="display: none;" and same happens
  • b
    I use a hx-get with hx.-trigger="every 10s" on a table that I want to keep updated. When I click on an item in this table it does an hx-swap on an invisible below every row in the table and shows data there. How can I avoid the hx-trigger to overwrite that "opened " and keep it, but still update everything around?
  • p
    @User I've been using SSE for live updating things rather than polling. It might be good for your use case?
  • b
    you mean something like this? https://github.com/fanout/django-eventstream
  • p
    Yup, I don’t do Django anymore, but that’s what I’m talking about. It’s not for all situations, but is fairly nice to be notified of updates instantly
  • b
    but there is no htmx way to do this?
  • b
    like exclude a part from an update?
  • p
    Oh, that is solving the problem from a different angle. There are other swap mechanisms and hx-preserve
  • c
    I am building a WebComponent and I have the component interacting with Forms using the 
    formAssociated
    property (https://html.spec.whatwg.org/multipage/custom-elements.html#custom-elements-face-example). This works perfectly fine with regular form POSTs but when I try to use this component with an 
    hx-post
    it doesn't pick up the value from the component. Does HTMX support this new feature?
  • m
    unfortunately not yet
  • m
    very sorry about that
  • m
    however you can use 
    hx-include
    to include it or a parent element
  • w
    It seems that clicking on a boosted link with an anchor (e.g., 
    <a href="/page/#middle">
    )doesn't put the anchor in the URL bar. It properly scrolls to the anchor, but I wasn't sure if the intention was that the anchor should also be pushed to the URL/history, or if perhaps something in my implementation is off.
  • p
    I'm wondering about the usage of 
    HX-Retarget
    with an HTTP redirect. The use case is this: we have a form:
  • p
    Copy code
    html
<form hx-post="/action" hx-target="this" hx-swap="innerHTML">
  • p
    if the form is invalid, we want to return the form fields with validation errors etc. However if it's valid we want to return a redirect without having to reload the page (.e.g with a client redirect),something like this:
  • p
    Copy code
    Location: /new-item/
HX-Retarget: body
  • p
    However it appears that the 
    HX-Retarget
    is ignored and the content of the new page is injected into our form. I'm just wondering what the right usage is?
  • m
    first thing to check: are you using the latest htmx
  • p
    yes - 1.6.1
1...541542543...1146Latest