-
Notifications
You must be signed in to change notification settings - Fork 328
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
Turbo Stream From and Browser Tabs #338
Comments
That's unfortunately up to browsers. When they choose to suspend updates. I know Safari is more aggressive about this. Not aware of anything we can do as web developers about this. |
@dhh I think this is a bug on Turbo. I have a chat an application that currently works on React. And we are porting all the stuff to hotwire. when the message is received an stimuls controller plays a sound on initialize() Videos, please turn volume on. React version: Screen.Cast.2023-10-19.at.9.09.49.PM.mp4Hotwire version Screen.Cast.2023-10-19.at.8.59.23.PM.mp4 |
now I'm trying to get a grasp on the code on Turbo. it seems that the issue could be in the stream_message_renderer which uses some sort of focusing |
@dhh note that I've replaced all the Screen.Cast.2023-10-19.at.10.22.18.PM.mp4 |
I have tried some things by replacing one by one and it seems that we should replace each call of nextAnimationFrame. |
Nice! This seems like a great improvement to the library |
I'm struggling with the PR right now, trying to pass just 3 specs from the complete test suite. |
Hello to all turbo developers, first of all, thank you for having such an amazing tool.
But currently on my site, my users have reported something to me that I hadn't noticed yet. On my platform some data is transmitted via callback with the broadcast to the turbo-stream-from tag.
The problem is that the DOM update, and the insertion or updating of elements only happen when we are directly in the site's tab, if we go to another tab, for example, when we come back, all the items that should have been rendered there, all come from once!
The text was updated successfully, but these errors were encountered: