# Bug or intended behavior when using respond\_to?

**URL:** <https://www.ruby-forum.com/t/bug-or-intended-behavior-when-using-respond-to/135764>\
**Category:** Rails\
**Created:** [April 24, 2008, 7:27pm UTC](https://www.ruby-forum.com/t/bug-or-intended-behavior-when-using-respond-to/135764 "2008-04-24T19:27:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dewie](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/ac8455/32.png) [@dewie](https://www.ruby-forum.com/u/dewie)\
**Post date:** [April 24, 2008, 7:27pm UTC](https://www.ruby-forum.com/t/bug-or-intended-behavior-when-using-respond-to/135764/1 "2008-04-24T19:27:09Z")

</div>

respond\_to do |format|  
format.js  
end

Works as expected in most instances. However…

Inside name-spaced controllers and custom REST actions I must specify…

respond\_to do |format|  
format.js { render(:layout =\> false) }  
end

Otherwise Rails complains about not being able to find a layout.

Anyone else seen this?