oscar perez wrote:
One of the problems is that if in the returned AJAX content is included any sx tag then if there is any javascript in the returned content this simply dissappears. I tried all the combinations with executeScripts separateScripts with no success however..
I've created several test apps looking at this and they all execute the inline scripts correctly. I believe you as it's a commonly reported problem, but it needs better isolation.
Another problem related to it is that I would like to be able to call callback functions after the returned content has been rendered. The workaround for that is to use afterNotifyTopics and timeouts but I dont think this is quite the same.
As far as I know, the widget does not fire an event "onContentReady" (ie. after the DOM has been updated and scripts executed). That would have been a nice feature.
And then the last problem is that I would like to use different targets to render the returned content based on the operation status.
Yeah, not supported in the current implementation.
Most likely these problems have solution with sx tags and it is just a problem that I don't have enough knowledge but after reading the documentation and ajax recipes extensively I couldn't find any answer to any of the above questions.
No, I think you're right there's no answers to these problems except possibly the first.
I've moved now to jQuery and all my problems are solved :)
Great idea and one that you won't regret. I moved to YUI for similar reasons.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
