I already commented at your blog... it's fixed in 4.1.2-SNAPSHOT
Julian Wood wrote:
Bug is reported, if anyone is interested.
https://issues.apache.org/jira/browse/TAPESTRY-1247
J
On 1-Feb-07, at 5:25 PM, Julian Wood wrote:
Okay I've posted a sample program to demonstrate the problem.
http
Bug is reported, if anyone is interested.
https://issues.apache.org/jira/browse/TAPESTRY-1247
J
On 1-Feb-07, at 5:25 PM, Julian Wood wrote:
Okay I've posted a sample program to demonstrate the problem.
http://jwoodchip.blogspot.com/2007/02/ajax-and-tapestry.html
I'm still hoping I'm missing
Okay I've posted a sample program to demonstrate the problem.
http://jwoodchip.blogspot.com/2007/02/ajax-and-tapestry.html
I'm still hoping I'm missing something silly, but maybe this is a bug?
Thanks,
J
On 31-Jan-07, at 8:46 PM, Julian Wood wrote:
Actually this is not yet solved. It turns
Actually this is not yet solved. It turns out it works in some cases,
but not in others. I've found it very difficult to track down when it
works, and when it doesn't work. I think I was fooled (previously)
into thinking it works when there is an error in the javascript in
the ajax response
Turns out this was actually a problem with a Border component and a
custom shell delegate - the Body component was not making it through
properly - all working now!
J
On 29-Jan-07, at 3:22 PM, Julian Wood wrote:
I have a div that is updated in response to an EventListener. This
is all fin
