https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • r
    It's technically possible to implement this with htmx by setting up delays and returning empty response from the server, but practically speaking, hyperscript would be a much better fit for this task
  • r
    _="init wait 3s then transition opacity to 0 then remove me" would do exactly what you want
  • f
    Cool! Will definitely look into that
  • b
    The best thing is that if you then decide you need just a liiitle bit of shiny, then what are you going to do? Rewrite in Vue, or just add one of these innocent HTML attributes? First one is always free!
  • s
    Yes, that's where htmx is great. In this case the developer who will work on this is not familiar with htmx yet, and it is just a small thing which we want done by friday (tomorrow). So introducing something new, even if it is simple, is an extra time eating thing.
  • b
    I think that's where enhance.dev could be interesting - start off with html files where the file path is the URL and then add complexity from there. Like PHP but with serverless deploys
  • d
    I notice that jinja2-fragments is not on the "Template Fragments" page. I found the htmx "Template Fragments" page from their Github repo. Their goal is to implement the "Template Fragments" pattern in the Jinja2 templating language often associated with Flask in the Python community. I've not tried it yet, but it looks interesting.
  • b
    7b? (Do we still do that?)
  • u
    hey folks, digging this old answers, withCredentials is barely documented
  • u
    Do you think this config is right?
  • u
  • u
    I am trying to create a basic demo of auth with a Deno API and an HTMX index.html, I've read a bit about "fetch" credentials settings, that are necessary for Set-Cookie to work, and probably also "mode: 'cors"
  • u
    both are on localhost but API is on "8000" and the webapp on "8080"
  • u
    I wonder what would be the equivalent setup in HTMX
  • u
    what bugs me is that I am not even sure what I should expect to see if it's correctly setup, probably some Access-Control headers
  • b
    fetch("http://localhost:8000/account/signup", { method: "POST", body: JSON.stringify({username:"foo", password:"barbar"}), credentials: "include"}).then(res => {}) this call works it seems for instance, that's what I am trying to reproduce
  • b
    The response only have Access-Control-Allow-Origin header, maybe that'rs related according to this answer: https://stackoverflow.com/a/48231372/5513532
  • a
    Guys has anyone had issues with select dropdown and option selected & disabled i.e placeholder in the dropdown box. Seems like hx-post always sends the default placeholder value rather than what user has picked. 😑
  • a
    When it's removed, all working as expected
  • a
    Any way around this?
  • m
    hmm, it should just be including the .value of the select
  • a
    Seems to pickup selected diaabled option (placeholder) and not user picked :/
  • m
    and this happens when the option is disabled?
  • m
    I bet .value is the culprit here
  • a
    I think thr fact that it's set to selected
  • m
    Normal select's work
  • m
    even if it starts w/ a selected value
  • m
    I could see disabling one causing it to use the default selected value though
  • m
    they aren't treated differently than any other input: they just ask the input for it's 
    .value
  • m
    I'll put together a codepen we can noodle with in a bit, have to get some work done
1...821822823...1146Latest