Disabling turbo drive on body with `data-turbo="false"` stops frames from working

1

Until now, we used opt-in strategy on out web - we had Turbo.session.drive = false, and used turbo-frames and streams in some places.

Now we wanted to allow Turbo Drive on part of the web. So I tried to delete `Turbo.session.drive = false`, and set data-turbo=”#{modern_page?}” to enable and disable turbo drive on pages based on whether they are ready for it.
In the documentation data-turbo is described as controlling Turbo Drive, not Frames or Streams.
However, frames (didn’t check streams) stopped working if data-turbo=”false” is set on body of old page.

Now that might be expected behavior, but the documentation doesn’t match that.
Is the documentation wrong, or is my web misbehaving for some other reasons?

2

@janpeterka that sounds like an issue with your application. I have a very similar situation on a project: Drive is globally disabled but I still use Frames. Not only are Frames working just fine but full drive behaviour is automatically enabled inside the Frame.

Unless you’re literally setting data-turbo=”false” on the frame element itself, the frames should work just fine even if inside an element where it is disabled.

Btw, depending on how you want to enable Turbo, you might find the root meta attribute useful, it allows you do enable Turbo on a subsection of your site, based on the path prefix: Turbo Handbook