Applied OutputEscapers should be removed when including a component from a view

A part of this problem is already exposed in ticket #509 (double escaping).

I could have sworn that the output escaping strategy could be set on the module level, not just application level. But, as this is not the case, I do not think that we should remove output escaping when including in a partial, but rather just prevent against double escaping.

It's not about partials. It's the component code expecting a variable to be of a certain type, e.g. a string, and not sfOutputEscaper.

I'll try to do an example:

Let's assume there's a class "Foo". Furthermore, let's assume there's a method or function somewhere else in the code which takes a parameter of class Foo like this:

function doSomethingWithFoo(Foo $foo) {...

Let's start. My action does

$this->bar = new Foo();

and symfony's view logic wraps an sfOutputEscaper around $bar, so in my view, I can call

<?php echo $bar->getName() ?>

without any problems. That's cool stuff! I don't have to care about quoting, things just behave well and coder friendly. Let's call a component from the view:

<?php include_component('mymodule', 'mycomponent', 'bar' => $bar) ?>

In the component's execute method looks like this:

public function execute() {
  doSomethingWithFoo($this->bar);
}

This call will fail as $this->bar is not of type Foo as expected, but of sfOutputEscaperObjectDecorator. Thus, I suddenly have to care about the escapers and call my component

<?php include_component('mymodule', 'mycomponent', 'bar' => $bar->getRawValue()) ?>

which is not what I'd expect from an automagic feature.