Fixed here https://github.com/rails/rails/commit/52b71c01fd3c8a87152f55129a8cb3234190734a Thanks you Jeremy ;).
On Tue, Nov 16, 2010 at 6:25 PM, Jeremy Evans <[email protected]> wrote: > On Sun, Oct 10, 2010 at 8:36 PM, Michael Koziarski > <[email protected]> wrote: >>>> Is it breaking your app some how? >>> >>> It breaks some test code, that's all. Test code that works on 5 other >>> web frameworks and previous versions of Rails. >>> >>> It's not a big deal either way, but I wanted to know rails-core >>> opinion before I decide whether to update my test code. >>> >> >> I'll see if I can get something a bit more definitive from josh as to >> why this was changed. Seems a toss up either way, but the current >> method is certainly a bit messy and at the very least we shouldn't be >> escaping / unescaping > > It's been a month since this was last discussed, and there doesn't > appear to have been any related changes made. Should I add a issue to > lighthouse so that it's easier to keep track of this? > > Jeremy > > -- > 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. > > -- 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.
