t:inputCalendar as popup with forceId="false" does not work
-----------------------------------------------------------

                 Key: TOMAHAWK-1484
                 URL: https://issues.apache.org/jira/browse/TOMAHAWK-1484
             Project: MyFaces Tomahawk
          Issue Type: Bug
          Components: Calendar
    Affects Versions: 1.1.10-SNAPSHOT
            Reporter: Ingo Hofmann


A popup calender with forceId="true" does not appear, but produces a JavaScript 
error when clicking on the button. The <span> element and JS code is rendered 
correctly, but the <input> element gets the wrong id (form ID missing).

Simple Facelet page that reproduces this issue (first calender works fine, 
second doesn't):

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml";
        xmlns:f="http://java.sun.com/jsf/core";
        xmlns:h="http://java.sun.com/jsf/html";
        xmlns:t="http://myfaces.apache.org/tomahawk";>
<h:head>
     <meta HTTP-EQUIV="Content-Type" CONTENT="text/html;charset=UTF-8" />
     <title>Calender test</title>
</h:head>
<h:body>

        <h:form id="calendarForm">

            <t:inputCalendar id="formWithForceIdTrue" 
monthYearRowClass="yearMonthHeader" weekRowClass="weekHeader" 
popupButtonStyleClass="standard_bold"
                currentDayCellClass="currentDayCell" 
                renderAsPopup="true"
                popupDateFormat="MM/dd/yyyy"
                forceId="true"/>

            <t:inputCalendar id="formWithForceIdFalse" 
monthYearRowClass="yearMonthHeader" weekRowClass="weekHeader" 
popupButtonStyleClass="standard_bold"
                currentDayCellClass="currentDayCell"
                renderAsPopup="true"
                popupDateFormat="MM/dd/yyyy"
                forceId="false"/>
        </h:form>

</h:body>
</html>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to