Thanks for the info! I don't think that's the culprit here, although I'll
keep in mind that multiple requests might not arrive in the order sent.
On Fri, Feb 25, 2011 at 11:04 AM, Rich M wrote:
> I can't say with any certainty this is your problem, but the one time I was
> having issues with a
I can't say with any certainty this is your problem, but the one time I
was having issues with an AJAX request being dumped and never showing up
server side there was a race condition. I had it listening to the click
event of a submit button, and on slower connections the form submit
would beat
To follow up... moving the first select out of the zone didn't help. I
didn't see how it would, was grasping at straws.
I finally avoided the problem by getting rid of the chained selects. I went
back to our older component that does the chaining with simple javascript
(stuffing all the possibl
Nope. In the failing cases, the ajax request did not arrive at my
AppModule's request filter. That's why the Select's onValueChanged() isn't
getting called. I don't think it's a case of Tapestry dropping the request
after it gets it.
On Fri, Feb 25, 2011 at 6:41 AM, Ulrich Stärk wrote:
> Can
Can you see the request hitting the server after the first zone's value is
changed?
Uli
On 24.02.2011 23:43, Bryan Lewis wrote:
> I've been trying to figure out a weird bug today, and before I lose the
> night over it I thought I'd ask the list. I'm using the cool new "chained
> select" feature
I've been trying to figure out a weird bug today, and before I lose the
night over it I thought I'd ask the list. I'm using the cool new "chained
select" feature. One Select has a zone, and triggers an onValueChanged()
method that affects another Select. It works fine on my machine and when
most
Do I need to use JS, like in the following example:
http://jumpstart.doublenegative.com.au/jumpstart/examples/javascript/ajaxselect1
?
On 20-12-2010 22:05, Mark wrote:
How are you setting up the Select to trigger an event?
On Mon, Dec 20, 2010 at 12:01 PM, Sergio Esteves<
sergio.este...@xpand
I'm not. Here's what I'm doing:
«
t:model="fieldModel" t:blankOption="NEVER" t:zone="valueZone"/>
${dateNow}
»
void onActivate() {
dateNow = new Date();
}
»
I see that the onActivate is called each time I change the value on the
select. However the date
How are you setting up the Select to trigger an event?
On Mon, Dec 20, 2010 at 12:01 PM, Sergio Esteves <
sergio.este...@xpand-it.com> wrote:
> Hi all,
>
> I have a select which updates a zone; that zone has a delegate that calls a
> function to return an active block. The problem is, when I chan
Hi all,
I have a select which updates a zone; that zone has a delegate that
calls a function to return an active block. The problem is, when I
change the value of the select that function is not called, what could
be wrong?
Thank you.
10 matches
Mail list logo