> After some digging, I can say it was done delibritely: > http://github.com/rails/rails/commit/856d2fd874d72dd9f83204affff4edfef3308361 > > Prehaps josh can enlighten us as to the reason why the change was > made, since the commit message does not do so.
Nor does the message here: http://github.com/rails/rails/commit/4dee277a9bc05083de6c831cf9aae0846849ecda Those commits don't really have any justification, so unless josh pipes up I'd be tempted to reverse them. However to play devil's advocate, the spec isn't exactly clear that they *should* be escaped, and nothing seems to break with them *not* being escaped. What makes you want them that way? Is it breaking your app some how? > Reversing that commit and > http://github.com/rails/rails/commit/1ee9b40b18a0bed5bb10a0785f7e2730bac983f6 > would probably fix things, if you decide to go that route. -- 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.
