So no script will ever get executed in the context of the AJAX request. Unlike the pprIFrame (which caused the browser to actually parse and render the whole page inside the hidden iframe, thus executing script also), an AJAX request is simply a receive of some text content through a pipe with no parsing or rendering of the content. The Trinidad PPR code receives the content through the pipe and parses the chunks and replaces the various elements in the page with these chunks. At this point the browser does re-render those elements, but then I believe we're then at the mercy of the browser implementation as to if it executes any script content or not.
On 8/9/07, Renzo Tomaselli <[EMAIL PROTECTED]> wrote: > > Thanks Danny, meanwhile I wonder why we shouldn't expect for a js chunk > included in a PPR target not to be executed at some point during the PPR > cycle. > Perhaps this is a matter of semantics, but I would expect the same > rendering behavior as for full page rendering. I mean js should execute > during PPR if part of a target. > Why an included script shouldn't get executed at all in IE ? Is this part > of Ajax specs (if any) to update dom but not to run js ? > > -- Renzo > > > > Danny Robinson wrote: > > Renzo, > > I suggest you don't count on this behaviour, as the 1.0.2 release due any > time soon switches to using AJAX rather than the _pprIFrame. This means > your script won't get executed at all in IE, and once in Firefox. There's > talk of some hooks into the AJAX routines to provide hooks when updates > occur to certain elements of the page, however there's a generic hook for > pre-and-post AJAX calls already in 1.0.2. > > AJAX powered PPR details are available here: > > http://myfaces.apache.org/trinidad/devguide/ppr.html > > Perhaps someone else can shed some light on a reliable mechanism to have > script snippets executed on PPR completion. > > Danny. > > On 8/9/07, *Renzo Tomaselli* <[EMAIL PROTECTED]> wrote: > > Hi, I noticed a strong asymmetry while executing a js block included > into a PPR target: on IE this runs once, in the context of _pprIFrame. > On FF it runs twice, once in the context of _pprIFrame and then in the > context of the original page, after PPR modifications have been applied > to the dom. > While on FF this behavior offers a full suite of tuning opportunities to > play with PPR contents, on IE the game is severely constrained. > Is that a bug to hunt for, a side-effect or a wanted feature ? > Thanks, > > -- Renzo > > > > > -- > Chordiant Software Inc. > www.chordiant.com > > -- Chordiant Software Inc. www.chordiant.com
