Re: [Trinidad] js error on PPR after client-side validation error

2008-01-14 Thread Matthias Wessendorf
Renzo, do you still see this ? -M On Nov 5, 2007 12:23 AM, Renzo Tomaselli <[EMAIL PROTECTED]> wrote: > > Matthias, here's a page chunk: > > > > simple="true" autoSubmit="true"> > > > value="#{bean.prop.integerValue}" rendered="#{bean.prop.int

Re: [Trinidad] js error on PPR after client-side validation error

2007-11-05 Thread Renzo Tomaselli
Matthias, here's a page chunk:                                                         ... Here selecting a type by "ptype" refreshes the panel, thus rendering a different input field. But in the meantime I discovered that if I use distinct ids for involved input fields - then the pro

Re: [Trinidad] js error on PPR after client-side validation error

2007-11-03 Thread Matthias Wessendorf
Can you post a simple page-code sniplet for that ? -M On 11/2/07, Renzo Tomaselli <[EMAIL PROTECTED]> wrote: > Hi, while using Trinidad v. 1.0.3, I forced a client-side validation > error by entering an invalid short number. > At the next PPR, I got a js error on Firebug: > > "e.getFacesMessage()

Re: [Trinidad] js error on PPR after client-side validation error

2007-11-02 Thread Renzo Tomaselli
More info: validation failure is not a necessary condition. I have a tr:selectOneChoice, which allows for choosing either a boolean or a number. Selection renders (through PPR from autoSubmit) either a tr:inputText or a tr:selectBooleanCheckbox. Now I select "number", enter a number and add it t

[Trinidad] js error on PPR after client-side validation error

2007-11-02 Thread Renzo Tomaselli
Hi, while using Trinidad v. 1.0.3, I forced a client-side validation error by entering an invalid short number. At the next PPR, I got a js error on Firebug: "e.getFacesMessage() is not a function" at line 6199 in Common1_0_3.js (in function _multiValidate). The involved line appears to be in