Yehuda Katz 4cbb9db0a5 For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self). ... * Additionally, instead of doing concat("</form>".html_safe), you can do safe_concat("</form>"), which will skip both the flag set, and the flag check. * For the first pass, I converted virtually all #html_safe!s to #html_safe, and the tests pass. A further optimization would be to try to use #safe_concat as much as possible, reducing the performance impact if we know up front that a String is safe.		2010-01-31 19:39:13 -08:00
..
active_model_helper.rb	For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).	2010-01-31 19:39:13 -08:00
asset_tag_helper.rb	For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).	2010-01-31 19:39:13 -08:00
atom_feed_helper.rb	Don't call additional methods on builders passed to the atom_feed helper.	2009-08-09 13:10:08 +12:00
cache_helper.rb	Make @controller an internal ivar in the view	2010-01-22 10:19:01 -06:00
capture_helper.rb	Switch to on-by-default XSS escaping for rails.	2009-10-08 09:31:20 +13:00
date_helper.rb	For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).	2010-01-31 19:39:13 -08:00
debug_helper.rb	For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).	2010-01-31 19:39:13 -08:00
form_helper.rb	For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).	2010-01-31 19:39:13 -08:00
form_options_helper.rb	For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).	2010-01-31 19:39:13 -08:00
form_tag_helper.rb	For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).	2010-01-31 19:39:13 -08:00
javascript_helper.rb	Reorg options_for_javascript and array_or_string_for_javascript	2010-01-30 16:13:49 -06:00
number_helper.rb	For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).	2010-01-31 19:39:13 -08:00
prototype_helper.rb	For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).	2010-01-31 19:39:13 -08:00
raw_output_helper.rb	For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).	2010-01-31 19:39:13 -08:00
record_identification_helper.rb	Added record identifications to FormHelper#form_for and PrototypeHelper#remote_form_for [DHH]	2007-05-14 17:30:35 +00:00
record_tag_helper.rb	API change: content_tag_for outputs prefixed class name	2009-10-08 14:13:49 -05:00
sanitize_helper.rb	For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).	2010-01-31 19:39:13 -08:00
scriptaculous_helper.rb	Reorg options_for_javascript and array_or_string_for_javascript	2010-01-30 16:13:49 -06:00
tag_helper.rb	For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).	2010-01-31 19:39:13 -08:00
text_helper.rb	For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).	2010-01-31 19:39:13 -08:00
translation_helper.rb	For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).	2010-01-31 19:39:13 -08:00
url_helper.rb	For performance reasons, you can no longer call html_safe! on Strings. Instead, all Strings are always not html_safe?. Instead, you can get a SafeBuffer from a String by calling #html_safe, which will SafeBuffer.new(self).	2010-01-31 19:39:13 -08:00