https://htmx.org logo
Powered by
# htmx-general
  • m
    "but SPAs are so much more reliable than web applications"
  • l
    Is there a possibility to edit the URL in hx-push-url? I have a separate view function that I call to get the updated content. E.g. my site: /home url to update content: /home/list?page=2 I wish to push /home?page=2 to the URL (without "list")
  • g
    I think there’s a response header that can do this
  • g
    I’d still like to expand that, though, to allow “false” as an option. But it should work for your use 😀
  • a
  • l
    @User cool, thanks! I would have to edit the header with a custom Django's middleware I assume, right?
  • a
    Yes, you have to set the response header server side when you return the response to an htmx request
  • l
    Fair enough. Some good ol' regex to edit the response header should solve my problems :D thanks!
  • f
    Hi,
  • f
    tags behave differently in terms of scope in htmx v1.50 and htmx v1.6.1. If we do hx-get for example and have the server return html with script tag that has a variable declared using 
    let
    . Lets say we do this twice - in htmx v1.5.0 these scripts would get executed in different scopes and there would be no errors. But in htmx v.1.6.1 these scripts probably get executed in same scope and javascript raises an error. I have added this to [htmx discussion on github](https://github.com/bigskysoftware/htmx/discussions/723#discussion-3747823). Can someone please advise how to deal with this in htmx v1.6.1? Thanks -
  • m
    answered on the discussion, but you need to wrap your javascript in a function so that the variables are not in the global scope:
    Copy code
    js
  (function(){
    //***** The line below gives error when more than one component is in the page ******//
    let fdz = document.getElementById("fdz_<%= @block.id %>")
    //More code implementing dropzone js
   )()
  • m
    as of 1.6, script tags act "normally" (as they do in regular web pages) where variables, etc. are part of the global scope
  • f
    Thanks so much!😀
  • c
    @mysterious-toddler-20573 thoughts on: https://github.com/bigskysoftware/htmx/issues/712 ?
  • m
    I think we have 2 of 3, we would just need an HX-Swap header
  • m
    I am fine w/ standardizing them
  • g
    C an htmx be useful to build an events celendar like Google Calendar? Any idea or pointers?
  • m
    telroshan has been implementing a pretty slick calendar view using htmx + javascript: https://twitter.com/search?q=as%20always%20htmx&src=typed_query&f=live
  • g
    Looks amazing. Its not open source, is it? Couldn't find it on github.
  • m
    nope, it's not unfortunately
  • c
    Here's something I don't think maintainers get to hear enough of: I wasn't getting 
    hx-ext
    to fire on elements without 
    hx-post
    or similar explicit attribute. But upgrading from version 
    1.6.0
    to 
    1.6.1
    fixed it. So now I have no questions to ask here, just: thanks for creating and maintaining this awesome tool. 💟
  • a
    There are organizations like healthcare that don't have good IT or there are legacy apps running that only run on IE. So these organizations healthcare and education have to keep running IE in order to not break their workflows
  • c
    Okay, now I do have a question: what's the idiomatic way to have 
    hx-ext="ignore:..."
    apply to non-htmx events in inner elements. Contrived example: say I want to disable the "remove-me" extension in some inner elements:
    Copy code
    <script src="https://unpkg.com/htmx.org/dist/ext/remove-me.js"></script>
<div hx-ext="remove-me">
    <!-- Removes this div after 1 second -->
    <div remove-me="1s">To Be Removed...</div>
    <div remove-me="1s" hx-ext="ignore:remove-me">To Be Removed...</div>
    <div hx-ext="ignore:remove-me">
        <div remove-me="1s">To Be Removed...</div>
    </div>
</div>
    In this case, all three elements are removed after one second, despite the "ignore". Would the remove-me extension need to check for ignores in inner elements itself 😨 or is there a better way to handle this?
  • a
    Guys, I'm really sorry if I missed this in search -- evaluating htmx for my project and need to support IE11. Is there any obvious pitfalls or should I be good to go? Reading up in the history of this discord I do see the maintainer commenting "x would break IE" so my inference is that IE support should be good to go so I will continue unless someone in this chat can tell me otherwise!
  • c
    I believe you are good to go with IE11! I happen to be on my Windows gaming box right now and I just checked my "big htmx examples page" (work in progress) in IE11 and it all works!
  • a
    It seems this is a sister project to hyperscript and was looking to that project to do some things as well. Do your examples happen to use a bit of hyperscript?
  • a
    thanks for looking at that by the way
  • g
    hyperscript does not support IE.
  • m
    htmx should work for IE11, but I have to admit I haven't been as diligent as I should be about testing it with the last few releases. Unfortunately the version of windows I have on vritual box is busted so I can't test. Can you run the tests here: https://htmx.org/test/1.6.1/test in IE11 and let me know the results (typically there are about 5 that are broken in IE, which are known issues)
  • m
    If there are any issues on IE, please let me know and I will fix them. For now, htmx is IE11 compatible.
1...468469470...1146Latest