Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stimulus controllers sometimes not connecting in Chrome after Turbo (frames or drive) navigation #700

Open
helhum opened this issue Jul 7, 2023 · 4 comments

Comments

@helhum
Copy link

helhum commented Jul 7, 2023

Seemingly MutationObservers are sometimes not firing in Chrome 1 2 3 4

This happened to me as well yesterday with Chromium Version 112.0.5615.137.

Restarting Chrome did help for me as well. Nevertheless it might be helpful to further investigate that and maybe file an issue with Chrome.

@marcoroth
Copy link
Member

Hey @helhum, do you have a reproducible setup so we can reproduce the issue you are describing?

@helhum
Copy link
Author

helhum commented Nov 16, 2023

@marcoroth unfortunately not really. I realised though, that closing the browser tab and loading the page in a new tab mitigates the issue. Until now, this only happened to me with a Vite development setup, never on a production site.

@sascha-egerer
Copy link

I had the same issue. Restarting Chrome solved it :-/ I have no idea...

@topherfangio
Copy link

I don't know if it's relevant to this issue, but I ran into something similar.

I put my data-controller directly on the <turbo-frame> tag and it was never reconnecting the controller. Moving it onto a <div> underneath the <turbo-frame> fixed the issue.

Hopefully this helps someone else who got to this issue from random Google searching 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants