[
https://issues.apache.org/jira/browse/TOMAHAWK-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893906#action_12893906
]
Leonardo Uribe commented on TOMAHAWK-1524:
------------------------------------------
In the demo of tomahawk 1.1.9:
http://svn.apache.org/repos/asf/myfaces/tomahawk/tags/1_1_9/examples/simple/src/main/webapp/calendar.jsp
We have multiple t:inputCalendar on the same page and the error is not present.
For now I'll close this issue as cannot reproduce. If you provide more
information about how to reproduce it please reopen this issue, so we can take
a look at it. The test was done using myfaces 1.1.7, so maybe it is related to
your myfaces implementation (it is better to use the latest one for 1.1.x
branch)
> Two pop-up calendars on the same page don't work
> ------------------------------------------------
>
> Key: TOMAHAWK-1524
> URL: https://issues.apache.org/jira/browse/TOMAHAWK-1524
> Project: MyFaces Tomahawk
> Issue Type: Bug
> Components: Calendar
> Affects Versions: 1.1.9
> Environment: Windows XP/RedHat Linux; Tomcat 6, Oracle iAS 10, Oracle
> Weblogic 10.3.1.0
> Reporter: Malova Anna
>
> Hello!
> I noticed the strange thing with pop-up calendars in MyFaces Tomahawk. I use
> MyFaces for JSF 1.1, Facelets 1.1.15 (when using 1.1.14 situation was the
> same). If I put the single pop-up calendar on my page, it works fine - pop-up
> is opened. But as soon as I put another pop-up calendar near the first one -
> for example, if I need to select a period - their pop-ups don't work. And if
> I use jsp instead of xhtml, i.e. MyFaces without Facelets, two pop-up
> calendars work fine again. What may be the reason?
> I have read another issue here (TOMAHAWK-1145) and tried to use the
> StreamingAddResource instead of DefaultAddResource - nothing was changed.
> Then I used the <t:document> tag instead of <html>, <t:documentHead> instead
> of <head> and <t:documentBody> instead of <body> - nothing was changed again.
> I tried to put these calendars in two different forms - again nothing was
> cahnged. Is there another solution of this issue?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
