You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Mark Faine (JIRA)" <my...@incubator.apache.org> on 2005/06/06 18:37:43 UTC

[jira] Created: (MYFACES-271) Inputdate component causes HTML validation to fail

Inputdate component causes HTML validation to fail
--------------------------------------------------

         Key: MYFACES-271
         URL: http://issues.apache.org/jira/browse/MYFACES-271
     Project: MyFaces
        Type: Bug
    Versions: Nightly Build    
    Reporter: Mark Faine
    Priority: Minor


Myfaces 1.0.9 - SVN sources from 6/6/2005.

I have the following in my JSP:

        <%-- effective date --%>
        <h:outputLabel id="outputLabel16" for="effectiveDate"
value="#{msg.nasageneral_effective_date}"/>
        <x:inputDate id="effectiveDate"
value="#{nasaGeneralBean.effectiveDate}" required="true" popupCalendar="true"/>
        <h:panelGroup id="panelGroup14">
          <h:outputLabel id="outuptLabel17" for="effectiveDate"
value="#{msg.common_required_char}" styleClass="requiredchar"/>
          <h:message id="message12" for="effectiveDate"/>
        </h:panelGroup>

When this is rendered the id gets broken into three:

id="form4:effectiveDate.day",
id="form4:effectiveDate.month",
id="form4:effectiveDate.year" 

The problem is that all of my "for" attributes refer to
form4:effectiveDate".  This causes a validation error when the validator
can't find the id given in the for attribute.

I've tried changing values for both the for attribute and the id attribute
but it seems to only cause more/different problems.

Thanks,
-Mark

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Closed: (MYFACES-271) Inputdate component causes HTML validation to fail

Posted by "Sylvain Vieujot (JIRA)" <my...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/MYFACES-271?page=all ]
     
Sylvain Vieujot closed MYFACES-271:
-----------------------------------

    Fix Version: Nightly Build
     Resolution: Fixed

Fixed by enclosing the all component in a span with the proper id.

> Inputdate component causes HTML validation to fail
> --------------------------------------------------
>
>          Key: MYFACES-271
>          URL: http://issues.apache.org/jira/browse/MYFACES-271
>      Project: MyFaces
>         Type: Bug
>     Versions: Nightly Build
>     Reporter: Mark Faine
>     Assignee: Sylvain Vieujot
>     Priority: Minor
>      Fix For: Nightly Build

>
> Myfaces 1.0.9 - SVN sources from 6/6/2005.
> I have the following in my JSP:
>         <%-- effective date --%>
>         <h:outputLabel id="outputLabel16" for="effectiveDate"
> value="#{msg.nasageneral_effective_date}"/>
>         <x:inputDate id="effectiveDate"
> value="#{nasaGeneralBean.effectiveDate}" required="true" popupCalendar="true"/>
>         <h:panelGroup id="panelGroup14">
>           <h:outputLabel id="outuptLabel17" for="effectiveDate"
> value="#{msg.common_required_char}" styleClass="requiredchar"/>
>           <h:message id="message12" for="effectiveDate"/>
>         </h:panelGroup>
> When this is rendered the id gets broken into three:
> id="form4:effectiveDate.day",
> id="form4:effectiveDate.month",
> id="form4:effectiveDate.year" 
> The problem is that all of my "for" attributes refer to
> form4:effectiveDate".  This causes a validation error when the validator
> can't find the id given in the for attribute.
> I've tried changing values for both the for attribute and the id attribute
> but it seems to only cause more/different problems.
> Thanks,
> -Mark

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (MYFACES-271) Inputdate component causes HTML validation to fail

Posted by "Mark Faine (JIRA)" <my...@incubator.apache.org>.
    [ http://issues.apache.org/jira/browse/MYFACES-271?page=comments#action_12320021 ] 

Mark Faine commented on MYFACES-271:
------------------------------------

Could you elaborate a bit on the fix for this issue.  I'm not sure I get it.

Thanks,
-Mark

> Inputdate component causes HTML validation to fail
> --------------------------------------------------
>
>          Key: MYFACES-271
>          URL: http://issues.apache.org/jira/browse/MYFACES-271
>      Project: MyFaces
>         Type: Bug
>     Versions: Nightly Build
>     Reporter: Mark Faine
>     Assignee: Sylvain Vieujot
>     Priority: Minor
>      Fix For: Nightly Build

>
> Myfaces 1.0.9 - SVN sources from 6/6/2005.
> I have the following in my JSP:
>         <%-- effective date --%>
>         <h:outputLabel id="outputLabel16" for="effectiveDate"
> value="#{msg.nasageneral_effective_date}"/>
>         <x:inputDate id="effectiveDate"
> value="#{nasaGeneralBean.effectiveDate}" required="true" popupCalendar="true"/>
>         <h:panelGroup id="panelGroup14">
>           <h:outputLabel id="outuptLabel17" for="effectiveDate"
> value="#{msg.common_required_char}" styleClass="requiredchar"/>
>           <h:message id="message12" for="effectiveDate"/>
>         </h:panelGroup>
> When this is rendered the id gets broken into three:
> id="form4:effectiveDate.day",
> id="form4:effectiveDate.month",
> id="form4:effectiveDate.year" 
> The problem is that all of my "for" attributes refer to
> form4:effectiveDate".  This causes a validation error when the validator
> can't find the id given in the for attribute.
> I've tried changing values for both the for attribute and the id attribute
> but it seems to only cause more/different problems.
> Thanks,
> -Mark

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Commented: (MYFACES-271) Inputdate component causes HTML validation to fail

Posted by "Sylvain Vieujot (JIRA)" <my...@incubator.apache.org>.
    [ http://issues.apache.org/jira/browse/MYFACES-271?page=comments#action_12320028 ] 

Sylvain Vieujot commented on MYFACES-271:
-----------------------------------------

Now, all the inputDate tags are enclosed in a span which has the expected id for the labels, ...
So the validation should not fail.

> Inputdate component causes HTML validation to fail
> --------------------------------------------------
>
>          Key: MYFACES-271
>          URL: http://issues.apache.org/jira/browse/MYFACES-271
>      Project: MyFaces
>         Type: Bug
>     Versions: Nightly Build
>     Reporter: Mark Faine
>     Assignee: Sylvain Vieujot
>     Priority: Minor
>      Fix For: Nightly Build

>
> Myfaces 1.0.9 - SVN sources from 6/6/2005.
> I have the following in my JSP:
>         <%-- effective date --%>
>         <h:outputLabel id="outputLabel16" for="effectiveDate"
> value="#{msg.nasageneral_effective_date}"/>
>         <x:inputDate id="effectiveDate"
> value="#{nasaGeneralBean.effectiveDate}" required="true" popupCalendar="true"/>
>         <h:panelGroup id="panelGroup14">
>           <h:outputLabel id="outuptLabel17" for="effectiveDate"
> value="#{msg.common_required_char}" styleClass="requiredchar"/>
>           <h:message id="message12" for="effectiveDate"/>
>         </h:panelGroup>
> When this is rendered the id gets broken into three:
> id="form4:effectiveDate.day",
> id="form4:effectiveDate.month",
> id="form4:effectiveDate.year" 
> The problem is that all of my "for" attributes refer to
> form4:effectiveDate".  This causes a validation error when the validator
> can't find the id given in the for attribute.
> I've tried changing values for both the for attribute and the id attribute
> but it seems to only cause more/different problems.
> Thanks,
> -Mark

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira