https://htmx.org logo
Powered by
# htmx-general
  • m
    pull requests welcome!
  • r
    What would you guys think of an hybrid approach to rendering the html content. If the client can use javascript render them on the frontend with a client side template, if they can't like a google web scraper deliver the html rendered from the backend. Is that a good idea? Or is it not worth the hassle?
  • g
    For me, personally, it was not worth the hassle.
  • g
    I thought about it, but realized pretty quickly that I'd need two exactly compatable rendering systems.
  • g
    By the time I've validated the user's request and waited for the database to return results, I either have to 1) render the result as a JSON file, or 2) just run it through my back-end template engine.
  • g
    I'd guess the template engine is a little slower than the JSON, but there's so much overhead involved in serving the rest of the request that the difference is non-existent.
  • g
    Now, I don't need to spend 50KB on a client-side templating engine (remember, that must be exactly compatable with my server) and the content arrives essentially pre-rendered and ready to shove into the DOM.
  • g
    It's a win-win-win...
  • g
    Unless you're using anything but Node.js on the back end, rendering on the client-side is a non-starter. And even then, I don't think the tradeoff is worth it. 🙂
  • g
    just demo'd htmx for a job interview and i'm pretty sure they loved it.
  • m
    Nice!
  • g
    Congrats! I hope you get the gig!
  • s
    Serious people like difficult things. You can't impress them with simple things. Don't be sad, if the are not amazed by htmx.
  • m
    Phew. Still almost 2% of our users on IE11.
  • k
    Q: I have a div that loads some content using htmx. The content in turn contains another element with a hx-get and hx-trigger set to "load". But it doesn't seem to fire. Is htmx ignoring content that is loaded asynchronously?
  • s
    try 'revealed' isntead of 'load'? .. htmx should process its own elements
  • s
    but if you load from another source you might need to call htmx.process(element)
  • s
    like if the element is generated by js then you need to manaully process() it.
  • k
    Got it, I loaded the first div using hyperscript using _on. Now using htmx-get for both and that works fine. I assumed hyperscript also used htmx internally 😎
  • m
    the integration story isn't perfect yet: hyperscript on htmx loaded content will get processed properly, but htmx doesn't process content loaded by hyperscript (yet)
  • s
    Hi. I'm struggling to get SSE working with a golang server. I can get 
    hx-ws
    working (I can see it 101 upgrades the connection from http to ws in the inspector and I can send and recv data), but when I use 
    hx-sse
    it immediately fails (inspector shows a "400 eventsource" attempting to do a GET, and no mention of upgrading to a ws). Have I missed out some kind of handshake needed for SSE to work? (The error on the backend when 
    hx-sse
    does its request is: 
    2021/04/07 15:22:11 upgrade:websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header
    )
  • m
    @User ☝️
  • m
    ben is our resident SSE and go expert
  • g
    I was gonna say. Dude, I am your guy.
  • g
    Not an expert. But I am also building an SSE server in Go.
  • g
    I can give you all the code you need 😇
  • s
    hooray! if you have a basic example of the server side for 
    hx-sse
    that would help me greatly 😄
  • g
    First, SSE and WebSockets are two different things. So it looks like you’re sending an SSE request to something that’s expecting websockets.
  • s
    Ah, my bad. I conflated the two.
  • g
    Yes. I also found several articles that got me started. Give me five minutes to get to my computer.
1...213214215...1146Latest