Turbostream not replacing the DOM

Well I’m lucky to have you onboard !

You right about your assumption about my goal.

To go straight to the point, this topic (more precisely this answer) say it all. Turbo intercepts form submissions and click events, and then creates its own request/response cycle. I haven’t finished to read the topic yet, I couldn’t wait for sharing it with you.

I’ll try the dispatchEvent approach, just to try it and see if it’s suitable for this need. It may be an overkill though, using regular XHR + DOM replacement may be a bit cleaner.

1 Like