|
Thanks both of you. I still have one doubt, though: using a placeholder as a page component provides both a DOM id to replace and a component to provide contents for replacement. However this game works just once: as soon as the placeholder is filled in with true contents from PPR, it's lost forever. While I can certainly create a new placeholder by js for a future PPR addition, there wouldn't be any associated component on the server side. In other words - an adding PPR response will fill the old placeholder without providing a new one. How can I force such a new component creation for the next cycle ? I'm afraid I miss the overall picture involving PPR restore-view and PPR rendering to solve this puzzle. -- Renzo Andrew Robinson wrote: Should have been partialTriggers. This is just to illustrate the usage. Simon's reply is correct.On Thu, Apr 10, 2008 at 11:42 AM, Andrew Robinson <[EMAIL PROTECTED]> wrote: |
- [Trinidad] how PPR response is applied to DOM Renzo Tomaselli
- Re: [Trinidad] how PPR response is applied to DOM Simon Lessard
- Re: [Trinidad] how PPR response is applied to DOM Andrew Robinson
- Re: [Trinidad] how PPR response is applied to... Andrew Robinson
- Re: [Trinidad] how PPR response is applie... Renzo Tomaselli
- Re: [Trinidad] how PPR response is a... Andrew Robinson
- Re: [Trinidad] how PPR response ... Renzo Tomaselli
- Re: [Trinidad] how PPR respo... Andrew Robinson
- Re: [Trinidad] how PPR respo... Renzo Tomaselli
- Re: [Trinidad] how PPR respo... Andrew Robinson
- Re: [Trinidad] how PPR respo... Renzo Tomaselli
- Re: [Trinidad] how PPR respo... Andrew Robinson
- Re: [Trinidad] how PPR respo... Renzo Tomaselli
- [Trinidad] inputText special characters Mathias Walter
- Re: [Trinidad] inputText special characters Kenneth Tang

