diff options
| author | Vipul A M <vipulnsward@gmail.com> | 2014-12-29 18:31:34 +0530 |
|---|---|---|
| committer | Vipul A M <vipulnsward@gmail.com> | 2014-12-29 18:31:34 +0530 |
| commit | 983674667a21ee2e4e6a43282507858634dce907 (patch) | |
| tree | 9dc977bf61224ffcaf93a714971c877b72482c9d /activesupport/lib/active_support/xml_mini/libxmlsax.rb | |
| parent | b67b57d47368b4b834cfe8c58d9e26f5c819c154 (diff) | |
| download | rails-983674667a21ee2e4e6a43282507858634dce907.tar.gz rails-983674667a21ee2e4e6a43282507858634dce907.tar.bz2 rails-983674667a21ee2e4e6a43282507858634dce907.zip | |
When trying to access a character on a string buffer object via `:[]`, if the object being accessed currently returns `html_safe?` as true,
we used to set `@html_safe` variable as true on new object created. When doing something like
x = 'Hello'.html_safe
x[/a/, 1]
would throw an error on ruby 2.2, since when nothign gets matched nil is returned by the code and it tries to set `@html_safe` value to true,
which would error since starting 2.2 nil is frozen.
This change adds a safety net to avoid setting `@html_safe = true` on frozen objects.
Fixes #18235
Diffstat (limited to 'activesupport/lib/active_support/xml_mini/libxmlsax.rb')
0 files changed, 0 insertions, 0 deletions