https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • g
    it is a disgrace that i can't get a masters in html
  • a
    I want a PhD in CSS.
  • b
    I've started getting quite a few `htmx:historyCacheError`s in the browser console after various requests (
    HX-Push
    header is being used). Are there any common reasons why this may occur or useful ways of seeing the cause of the error in more detail? My guess is that the size of the content on the page is too large for it to be cached, but I have no real reasoning behind that.
  • g
    After getting hooked on HTMX I decided to make a full stack framework from it using Express. Please have a go, make suggestions etc hacked it together in 2 days, so it’s rough around the edges. But I’m quite enjoying playing with it so far. The idea is that it is config free, and relies on a sort of NextJS server side routing structure to define all the endpoints. And Mustache to render the htmx that is served. I’ll be coding up some examples shortly. https://www.npmjs.com/package/htmxx
  • e
    With the 
    throttle
    option on 
    hx-trigger
    , can that be applied across multiple events? For example, I want to trigger a request whenever a click or a 
    mousemove
    , 
    touchstart
    , or 
    scroll
    action happens, but I want to throttle all of those collectively, so that requests fire no more than every 30ms.
  • e
    I think I can do that manually with the event filters, like 
    hx-trigger="mousemove[checkForGlobalThrottle()], touchstart[checkForGlobalThrottle()], scroll[checkForGlobalThrottle()]"
    but I'm hoping there's a cleaner way
  • e
    Also, separate question, can I have multiple separate triggers associated with separate requests? For example, on one element, could I have a 
    click
    send one request, and a 
    mouseover
    send another request?
  • a
    Shoot I got spoiled. I now find easier to do things with native HTML (+ htmx) with some sprinkled hyperscript than dealing with a fancy-library component and Angular.
  • e
    When using 
    htmx.ajax
    , is there a way to add a callback for errors, just for that request?
  • e
    I know I can set up a listener for 
    htmx:responseError
    on that element, but that would catch all instances of htmx errors on that element. I just want to set it up temporarily, for that one request
  • e
    I thought I'd be able to do it by chaining 
    .then()
    , but it seems no data gets passed to that callback. Same for 
    catch()
    .
  • e
    Anyone know if I can use Idiomorph to clone the options in one select to another select?
  • e
    Hmmm... we may need a channel for Idiomorph 🙂
  • e
    Also might somewhat be overkill for what I need. Reexamining my problem.
  • p
    Has this issue been created/implemented? I could use 
    htmx:redirectReceived
    to force a full page reload when it happens (Usually when the user is no longer logged on).
  • t
    Does the idiomorph extension work for oob swaps?
  • t
    hmm initial tests are throwing "too much recursion". I'll need to look at this in more detail
  • t
    I clearly have no clue how to use idiomorph. I tried swapping the whole body instead of using the oob I was doing and it just nuked my entire DOM
  • t
    wait no, that's not an idiomorph issue
  • f
    Hey everyone
  • f
    How can I run some javascript when the AJAX request completes?
  • f
    Copy code
    html
    <select class="selectpicker form-control" hx-post="{% url 'hypervisors' %}" hx-target="#hypervisor-select"
        id="region-select" name="region" hx-trigger="change">
        <option disabled selected>Choose region</option>
        {% for region in regions %}
        <option value="{{ region }}">{{ region }}</option>
        {% endfor %}
    </select>
  • f
    So for example when #hypervisor-select has been replaced by HTMX, I'd like to run some javascript. Is this built in?
  • w
    I think you can listen to the htmx:afterSwap event
  • f
    thx 🙂
  • m
    you need help with this?
  • m
    idiomorph is.... quite new.
  • t
    I will, tomorrow. Currently working on a different project
  • m
    roger, I will be available in the morning MST
  • t
    The DOM nuke wasn't idiomorph though, it was happening with 
    outerHTML
    too
1...832833834...1146Latest