Defined controller layout always gets used

[hotwired]

Defined controller layout always gets used

[acetinick]

I have a workaround here that I ended up using for layout methods,

class TestController < ApplicationController
  layout -> { turbo_frame_request? ? false : "custom" }
end

This similar logic exists in Turbo::Frames::FrameRequest

[stgm]

We discussed at https://discuss.hotwire.dev/t/turbo-response-always-using-layout-from-controller/1713/

Let me mention my use case, which does require the availability of layouts, so it doesn't get lost in the discussion.

In my application there are a lot of settings/administration screens that are presented in an easy-to-dismiss modal dialog. All of these screens have their own controllers and they are loaded on demand. To clean up the views, I have actually put all of the boilerplate into a layout and assigned this layout to each of the relevant controllers.

<turbo-frame id="modal">
<div class="modal-content">
    <% if content_for?(:title) %>
    <div id="modal-browser-header">
        <%= yield(:title) %>
    </div>
    <% end %>
    <div id="modal-browser-body">
        <%= yield %>
    </div>
    <% if content_for?(:footer) %>
    <div id="modal-browser-footer">
        <%= yield(:footer) %>
    </div>
    <% end %>
</div>
</turbo-frame>