From: "eike.rb (Eike Dierks)" Date: 2012-04-03T14:07:18+09:00 Subject: [ruby-core:44097] [ruby-trunk - Bug #6213] Builder::XmlMarkup drops html_safe Issue #6213 has been updated by eike.rb (Eike Dierks). shyouhei (Shyouhei Urabe) wrote: > I guess it is the builder gem. Hi Shyouhei, you're probably right that this is in a third party gem, but the xml builder is quite a central gem. so you might want to give me some advice, to whom I'd should report this? Thinking about that, I'd really want to get the builder into the core of ruby. So that we can improve on the builder within here. I'd like to improve the builder, so that it would work nicely with the html_safe of rails3 Which actually boils down to not escaping things, that do have the safe flag set. And declaring all output of the xmlbuilder html_safe by definition. It was not really easy to inject into the current xmlbuilder. And it's not yet really safe. I want to get the builder into the core of ruby (and rails) and to make it a first line aproach for building markup. And I want to make it really safe. I had a close look at the code base of the builder, (it works quite well as of today) But we might need to rewrite that. But the builder concept is big! ---------------------------------------- Bug #6213: Builder::XmlMarkup drops html_safe https://bugs.ruby-lang.org/issues/6213#change-25626 Author: eike.rb (Eike Dierks) Status: Third Party's Issue Priority: Low Assignee: Category: Target version: ruby -v: 1.9.2 A single line in Builder::XmlMarkup needs to be changed slightly, to enable the builder to work with the html_safe flag that was introduced with rails3. like def method_missing(sym, *args, &block) [...] text = arg.to_s # changed this line to keep the html_safe flag -- http://bugs.ruby-lang.org/