[Trinidad] Client-side validation of conditionally disabled inputText
Hi! I have some problem with client-side validation (CSV) of conditionally disabled field marked as required. Let's say that there is some inputText: Intially, bean.disabled is true, so inputText is disabled and if we try to submit relative form no "value required" errors will issue. However, if: 1. some event change bean.disabled to false and trigger ppr with that input, and after that 2. some other event change bean.disabled back to true and ppr that inputText yet again then inputText will still be marked as required field on client, though it is disabled. It leads CSV to issue error in FF on disabled field and to "cannot focus disabled element" error in IE. Sadly, it renders whole form totaly unusable :( Am I missing some special configuration? Thanks.
Re[2]: [Trinidad] Client-side validation of conditionally disabled inputText
... somebody replaced libs in our main repo with last 1.0.3 snapshot. Didn't notice it in the first place. False alarm. Thanks for pointing out where to look :) > > Which version of Trinidad? > > On 8/30/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Hi! > > I have some problem with client-side validation (CSV) of conditionally > > disabled field marked as required. > > > > Let's say that there is some inputText: > > > > > > Intially, bean.disabled is true, so inputText is disabled and if we try to > > submit relative form no "value required" errors will issue. > > However, if: > > 1. some event change bean.disabled to false and trigger ppr with that > > input, and after that > > 2. some other event change bean.disabled back to true and ppr that > > inputText yet again > > > > then inputText will still be marked as required field on client, though it > > is disabled. > > It leads CSV to issue error in FF on disabled field and to "cannot focus > > disabled element" error in IE. Sadly, it renders whole form totaly unusable > > :( > > Am I missing some special configuration? > > > > Thanks. > > > > > > -- > Chordiant Software Inc. > www.chordiant.com > >
Re: Table PPR problem when trigger Outside
Have you by any chanсe tried 'partialTriggers="::removeAll"'?
tr:table is NamingContainer, so partialTriggers must be of special form when
you refer components outside it from one of it's columns (or components inside
tr:table from outer ones).
>
>
>
> Hi,
> I have a Requirement that when i select BooleanCheckBox which is
> outside the table with autosubmit,i need to trigger the value to inside the
> Table column,
>But the Value is Not trigged,I think the problem with the
> partialTriggering ID because When i place both components in the same
> Column,working fine.
> Sample Code:
> binding="#{backing_first.removeAll}"
> id="removeAll" autoSubmit="true"/>
>
>id="remove1"
> partialTriggers="removeAll"/> ...
>
>
> Please Suggest me how can rectify the Problem..
> I have seen some of the posts but this requiremnt is reverse to that.
>
> Thanking You,
> Ramesh.
>
> --
> View this message in context:
> http://www.nabble.com/Table-PPR-problem-when-trigger-Outside-tf4370599.html#a12457228
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
Re: Table PPR problem when trigger Outside
'partialTriggers="MyTable:removeAll"' will certainly have no effect in code
snippet you provided.
If you refer checkbox just outside of tr:table from that table's column, then
trigger component refid should begin with "::", not some other id.
>
> Hi,
>Yes,I tried with 'partialTriggers="MyTable:removeAll"' eventhough no
> Effect.
>Please let me out from this issue.
> Thanks for Reply...
>
>
>
> Vadim Dmitriev wrote:
> >
> > Have you by any chanсe tried 'partialTriggers="::removeAll"'?
> > tr:table is NamingContainer, so partialTriggers must be of special form
> > when you refer components outside it from one of it's columns (or
> > components inside tr:table from outer ones).
> >
> >>
> >>
> >>
> >> Hi,
> >> I have a Requirement that when i select BooleanCheckBox which is
> >> outside the table with autosubmit,i need to trigger the value to inside
> >> the
> >> Table column,
> >>But the Value is Not trigged,I think the problem with the
> >> partialTriggering ID because When i place both components in the same
> >> Column,working fine.
> >> Sample Code:
> >> >> binding="#{backing_first.removeAll}"
> >> id="removeAll" autoSubmit="true"/>
> >>
> >>>> id="remove1"
> >> partialTriggers="removeAll"/> ...
> >>
> >>
> >> Please Suggest me how can rectify the Problem..
> >> I have seen some of the posts but this requiremnt is reverse to that.
> >>
> >> Thanking You,
> >> Ramesh.
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Table-PPR-problem-when-trigger-Outside-tf4370599.html#a12457228
> >> Sent from the MyFaces - Users mailing list archive at Nabble.com.
> >>
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Table-PPR-problem-when-trigger-Outside-tf4370599.html#a12459529
> Sent from the MyFaces - Users mailing list archive at Nabble.com.
>
