This didn't work. Examining the response (via alert(response)) shows
the following:
1) with only evalScripts set to true, all the script tags are stripped
off.
2) with evalResponse set to true, the script tags aren't stripped off
but aren't evaluated, either.
On 1 nov, 07:55, Oskar Krawczyk <[EMAIL PROTECTED]> wrote:
> Hi Raphael,
>
> using update option might just not do the trick – I remember having
> some troubles with it myself – have you tried doing a:
>
> ...
> onComplete: function(response) {
> $('responseDiv').set/inject/append(...) // pick one, considering
> what is your response
> }
> ...
>
> Best,
> Oskar
>
> On Oct 31, 8:13 pm, Raphael Gomes <[EMAIL PROTECTED]> wrote:
>
> > Greetings,
>
> > I'm building a site that relies heavily on Ajax responses that include
> > Javascript.
>
> > In 1.1 this wasn't a problem and if I had a code like:
>
> > $('myForm').send({
> > method: 'post',
> > evalScripts: true,
> > update: $('responseDiv')
>
> > });
>
> > it would fetch the server response to myForm, update responseDiv with
> > it and execute all scripts in the response.
>
> > Now in 1.2, I'm writing this code as:
>
> > $('myForm').set('send',{
> > method: 'post',
> > evalScripts: true,
> > update: $('responseDiv')
>
> > }).send();
>
> > and I find that it ignores all the scripts on the response. Using
> > evalResponse (alone or in combination with evalScripts) didn't help
> > either.
>
> > Any ideas?
