> I've run into the same issues with render_to_string and there was some > discussion and I think it basically boiled down to it being a bug. I > don't think it should mess with the current rendering either, but I'm > not sure if this has been looked at for 2.0.
If you have a test case which exposes this, we can take a look. There have been some changes to how render_to_string works, so hopefully we've fixed this for you, but the best way to know for sure is to write a test case for us :) -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
