https://htmx.org logo
Powered by
# htmx-general
  • m
    push come shove on the scroll issue. you could probably catch the 
    htmx:afterSwap
    event and scroll the video into view (if I'm understanding the problem correctly)
  • m
  • m
    will go out w/ 1.3.0
  • m
    @User @User @User I opened a pull request against dropzone w/ DOM event support: https://github.com/dropzone/dropzone/pull/1925
  • m
    looks like he accepted it:
  • m
  • m
    So once this is released you should be able to do something like this:
    Copy code
    html
<div hx-trigger="dropzone:complete" 
     hx-get="/whatever">
    <form action="/file-upload"
          class="dropzone">
      ...
    </form>
</div>
  • m
    That'd make a great demo for the examples pages
  • m
    a button that loads a dropzone and then gives a nice message when it's complete
  • l
    @mysterious-toddler-20573 that's awesome. Really love your project! Thanks for all your hard work and time!
  • m
  • m
    Congrats! Can you explain a bit more what the target and consume modifiers do? Target allows listening to events on elements that may not be on the page right away? And consume stops the propagation of an event? Couldn't find anything documented for 
    consume
    other than the release note. A great update as usual.
  • m
    Yep need better docs but that’s the gist
  • s
    I am getting CORS error for github api, how do I fix this?
    Copy code
    html
<button type="button" hx-get="https://api.github.com/users/rajasegar" hx-target="#profile">Get Profile</button>
    The same request works with fetch api, Please help
  • s
    console log
  • s
    The error states the problem, your get request with htmx is not considered a 'simple request' (thus subject to cors) because it includes the hx-trigger header.
  • s
    the 'normal' fetch request does not have this header and thus the cors doesn't enforce a cors policy on it.
  • s
  • s
    So how do I make cross origin requests with htmx? Is there any recommended way?
  • m
    It looks like you might want to delete the 
    HX-Request
    header
  • m
    you can do that with the 
    htmx:configRequest
    event
  • m
    Copy code
    event.details.headers = []
  • g
    You can also configure your server to allow cross-origin resource sharing. There are some headers that your server can return that will disable this safety feature.
  • g
    -- yes, you should consider it as disabling a safety feature in your clients' browsers, but there are legitimate reasons to do so, once you've analyzed the situation.
  • g
    It's a pretty common stumbling block for any AJAX-y web application. I had to do a crash course in CORS when I built my first Angular app. 😦
  • s
    ya, in general you want to configure cors at the webserver level, I sadly see a trend that is letting cors requests hit application code and handling it in middleware... I suspect for exactly the reason that developers don't want to learn about it 🙂
  • s
    (also sometimes you legitimately cannot change the webserver config)
  • s
    also for most 3rd party api you should generally have the request go frontend -> backend -> 3. party .. instead of calling the api directly in the user browser.
  • m
    Anybody here know websockets in python
  • m
    ?
1...172173174...1146Latest