https://htmx.org logo
Powered by
# htmx-general
  • m
    make it so
  • g
    i'm pretty sure carson is the only person who can build the htmx website
  • m
    lol
  • h
  • h
    I found a bug in my docs from hx-locate but can't test locally
  • h
    so I can push up a fix without testing
  • h
    which is why the bug is there in the first place
  • m
    šŸ‘† what ur discord thinks u look like šŸ‘‡ what u actually look like
  • m
    the state of building a web site in 2022
  • m
    ben, when are you porting this all to some go thing w/ no dependencies?
  • b
    Are you pushing the URL of the fragment HTML response to the browser history? If so, you probably need to make that fragment into a complete page, and use hx-select to get the fragment out when called by htmx.
  • a
    if I set a 
    value
    attribute to a 
    th
    element, like 
    <th value="2022-06-06" id="start_date" name="start_date">2022-06-06</th>
    , should an 
    hx-include=#start_date
    be picking it up?
  • a
    (it seems no, but I want to check if it's desired functionality)
  • b
    I don't think so Sergi, but 
    <th><input ... /></th>
    should work. Is that feasible for you?
  • a
    Inserting an input like this? 
    <th><input id="start_date" name="start_date" value="2022-06-06">2022-06-06</th>
  • a
    the header gets then rendered as in input field:
  • a
    the right approach would probably be to use a 
    data-
    attribute, but then I can't easily grab that value with hx-include.
  • g
    <input type="hidden">
  • b
    there is also hx-vals and hx-vars to consider, which I can never remember the distinction between
  • b
    You can also reset the input style and use 
    readonly
    to make it indistinguishable
  • b
    I think Deniz is right that hidden input is the canonical answer. hidden inputs have been used since the beginning of time
  • a
    oh, right šŸ¤¦ā€ā™‚ļø
  • a
    ok, I'll roll will that for now
  • b
    I'm basically guaranteed to always have AN answer, and it's like 1/1000 that it's a GOOD answer. Should probably let people know that when I respond
  • a
    thanks! šŸ˜„
  • a
    I am looking for an example in the docs of how to respond to a custom htmx event such as 
    htmx:afterRequest
    in JS. Can I just do 
    someElm.addEventListener('htmx:afterRequest', () => { // do stuff })
    ?
  • b
    Yes you can Jonah, if 
    someElm
    is the element with the 
    hx-*
    actions
  • d
    hello
  • d
    there is some group or room of flask-htmx
  • b
    There is #941388608290574336 and #864934037381971988 , no flask specific yet. 1cg can make you one if you'd like
1...704705706...1146Latest