https://htmx.org logo
Powered by
# htmx-general
  • b
    I suppose I just can't grok the browser without listeners. (yet)
  • g
    Here is the entire page when the codeigniter 4 debug bar is enabled for site development.
  • m
    Can you change the htmx import to 
    https://unpkg.com/htmx.org@1.6.0/dist/htmx.js
    and see where the exceptions are occurring?
  • m
    the only thing I can think of is that it is interacting poorly w/ some other script
  • m
    this is very straight ahead htmx
  • m
  • m
    this code is working for me here ☝️
  • m
    maybe there is something in the html you are returning?
  • g
    Your JSFiddle doesn't include the js code injected by codeigniter development mode as shown in the text of the page I sent - my guess is that's where the problem comes from? Here is the first error that is shown in the console.
    Copy code
    Uncaught DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
    at evalScript (https://unpkg.com/htmx.org@1.6.0/dist/htmx.js:1425:28)
    at processScripts (https://unpkg.com/htmx.org@1.6.0/dist/htmx.js:1432:17)
    at https://unpkg.com/htmx.org@1.6.0/dist/htmx.js:569:17
    at https://unpkg.com/htmx.org@1.6.0/dist/htmx.js:2562:38
    at forEach (https://unpkg.com/htmx.org@1.6.0/dist/htmx.js:239:21)
    at doSettle (https://unpkg.com/htmx.org@1.6.0/dist/htmx.js:2561:29)
  • m
    That’s my guess: a conflict w codeigniter (not familiar w it)
  • s
    Using encoding form-data always is a good idea. One condition less in the code. At least in one of my projects this works fine since several years. But this does not use htmx yet.
  • g
    I just happened to look back at a test app that I played with back in April using codeigniter 4 and the then htmx 1.3.3. Codeigniter debug bar works in that app. So I just switched out this code to use 1.3.3 and the problem disappeared. So I decided to try 1.5.0 - it works! Breaks with 1.6.0. Update: pulled 1.6.0 down to use as local, replace the evalScript in 1.6.0 (as it is causing the error) with the old one from 1.5.0 and the errors go away. The problem appears to come from codeigniter injecting its own script tags which htmx then has a problem with due to the way it injects its script code.
  • l
    Not sure what you mean there - is it a good idea to always use multipart/form-data? Was that what you were saying? In the end, that is what I'm doing. It just seems like I have to do it using hx-encoding and not just setting the enctype attribute on the form element.
  • l
    When using boosting (via 
    hx-boost
    ), it looks like I need to actively set all default HTML elements to 
    hx-swap="none"
    if the responses solely consist of 
    hx-swap-oob="…"
    elements. Would it make sense to allow HTMX to detect that case and prevent the default body swap?
  • m
    thats worth thinking about
  • m
    maybe a response header?
  • l
    That'd work, I guess. I wouldn't mind a dedicated media type as strictly speaking what we return is not proper 
    text/html
    but rather individual elements only, that only HTMX would know how to process anyway.
  • m
    media type is an interesting idea
  • m
    want to create an issue and do some reasearch? And maybe a pull request?
  • l
    That's what Hotwire uses. 😬
  • m
    🤷 if it's the right thing, I'm OK with it
  • m
    I like the ability to switch the swap style in the response
  • m
    in general
  • l
    I can definitely create a ticket. I've never coded JavaScript at all, though.
  • m
    there's always a first time
  • l
    But it's JavaScript! 😂
  • m
    if you are smart enough to type the words "dedicated media type" you are smart enough to write javascript
  • l
    Maybe smart enough, but not at the right level of insanity yet.
  • m
    \> one... of... us... \> one... of... us...
  • l
    Hm, wondering if checking whether the response has an 
    <html>
    or 
    <body>
    element as its root would be enough already. 
    hx-boost
    is currently defined to target 
    <body>
    by default, so that would sort of align.
1...424425426...1146Latest