https://htmx.org logo
Powered by
# htmx-general
  • m
    does that work for you?
  • m
    I think the docs page needs to be updated
  • b
    Okay. I'm not crazy 🤪
  • m
    if you omit the protocol it should default to 
    wss
  • m
    No, you aren't crazy
  • m
    well
  • b
    Sounds good. I'll submit a quick PR for docs if that helps.
  • m
    this particular situation does not prove you are crazy
  • g
    I hope I didn’t break something. If so, sorry!
  • m
    no, just a docs bug
  • g
    Phew!
  • m
    there are no bugs in htmx, just happy little accidental pull request opportunities
  • b
    No worries. This is my first time messing with WebSockets, and I just needed to know if it was something I was doing wrong or if the docs needed changing.
  • m
    👍
  • m
    @User htmx contributor
  • b
    Yay! PR submitted.
  • m
    and accepted
  • b
    Bam! And just like that the notifications alert display in my header nav doesn't need page refreshes! Just swap in the alert and drop-down with the latest notifications when there's a change via websocket. One line of code needed changed on the front-end and a few extra lines in the back instead of a page-and-a-half of js hell.
  • b
    I'll test tomorrow and let you know.
  • u
    Ok yeah it seems I've completely fixed the bug with the history in our project. The last odd bug was just the way our flask rendered the templates and needed one function to check for 
    if 'HX-History-Restore-Request' in request.headers:
    for everything to work. Will confirm tomorrow.
  • u
    Ok so confirmed the problem was't minification, but I don't really get what I did to fix it though
  • b
    In what state is your app now? I wanted to jump on board to help solve the history issues this week.
  • u
    Just pushed the fixes to production and it seems to work. Used history-elt and hx-preserve with the new hx-history-restore-request headers
  • b
    In case your issue is related to this, maybe you can provide some insight? https://github.com/bigskysoftware/htmx/issues/370
  • u
    I see you've narrowed it down a bit already? I kinda worked around the core issue just to get things working, without knowing what caused the problems in the first place. And the problems were a bit different than with the poster. Could have the same root cause though. 🤔
  • a
    Hi guys, just a quick one if someone can help?
  • a
    Essentially, I'm using django with htmx, i've got a base template which then performs a get request to load the actual content. This works great aside from breaking the browser "back" button - which loads just brings back the internal content
  • a
    Any ideas how I fix/compensate for this?
  • g
    Simple questions first -- are you using 
    hx-push-url
    ?
  • a
    I've tried experimenting with it, both at the inner content and base template level
1...150151152...1146Latest