I solved it on my project.
The problem was due to a conflict between inMethod's grid yui and wicket
yui. Although I updated both of them to use the same yui version, this
didn't fix my problem - the calendar would still not show.
Then I moved the code that generated the grid after the one that created the
calendar. This did it.
I think the real problem is including yui twice. And I think this was
discussed a lot in this mailing list. I don't know if a real solution was
found though.
Cristi Manole
On Wed, Jul 16, 2008 at 5:11 AM, Cristi Manole <[EMAIL PROTECTED]>
wrote:
> I'm running on (quite) the same config.
>
> Anyways, I think Serkan is right - > if you have an ajax component on the
> page the date text field will stop working. He has another date text field,
> I have a single date text field but on a modal window implemented as a panel
> (if that even matters).
>
> I think *the problem is here *:
> ->line 273 DatePicker
>
> if (AjaxRequestTarget.get() != null)
> {
> final String javascript = "var e = Wicket.$('" +
> getEscapedComponentMarkupId() + "Dp" +
> "'); if (e != null && typeof(e.parentNode) !=
> 'undefined' && " +
> "typeof(e.parentNode.parentNode != 'undefined')) " +
> "e.parentNode.parentNode.removeChild(e.parentNode);";
>
> response.renderJavascript(javascript, null);
> }
>
>
> [javascript =
> var e = Wicket.$('i1d6Dp'); if (e != null && typeof(e.parentNode) !=
> 'undefined' && typeof(e.parentNode.parentNode != 'undefined'))
> e.parentNode.parentNode.removeChild(e.parentNode);]
>
> This piece of code gets executed when I'm inside an ajax request (which is
> our case). I think what it tries to clean is not doing very well. When I
> have a (one) date text field on a regular page, that code will of course not
> get executed. So I guess it's erasing yui magic, not cleaning up the html.
>
> The only reason for the fact that the examples in wicket work (for modal +
> date thingy) is because instead of an <input> tag, the date*field *uses
> <span> or <div>...
>
>
>
> On Tue, Jul 15, 2008 at 3:53 PM, Serkan Camurcuoglu <[EMAIL PROTECTED]>
> wrote:
>
>> No, my configuration is Tomcat 5.5.23 Jetspeed 2.1.3 Wicket 1.3.4 and
>> Firefox 2.0 on Linux.. Do you know which file was patched for the safari
>> problem? This could be a pointer to find the cause of the problem..
>>
>> Regards,
>>
>>
>>
>>
>>
>> Ryan Gravener wrote:
>>
>>> Are you guys using safari? If so I think this problem is patched in
>>> 1.3.4.
>>>
>>> On 7/15/08, Serkan Camurcuoglu <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>>> I'm not sure about the reason, but in my portlet application, only one
>>>> of the date pickers is initialized if I add two portlets on the same
>>>> page containing date pickers, so only one of them works.. also it seems
>>>> like the date picker doesn't work if there is any other wicket ajax
>>>> component loaded on the page.. I think it's a problem with the
>>>> wicketCalendarInits array object which is used for initializing these
>>>> date pickers, but I haven't found the exact cause yet, I'd like to hear
>>>> if you find a solution..
>>>>
>>>>
>>>> Cristi Manole wrote:
>>>>
>>>>
>>>>> Hello,
>>>>>
>>>>> Any ideas why the calendar does not show on my modal window?
>>>>>
>>>>> ->I've seen the examples and I know it's working.
>>>>> ->It is not a problem related to z-index
>>>>>
>>>>> *It seems the yui class does not get appended to the tag so clicking
>>>>> the
>>>>> calendar icon does nothing (i presume that's the reason).
>>>>>
>>>>> *Has anyone by any chance experienced this or something similar? Any
>>>>> suggestion is highly appreciated :).
>>>>>
>>>>> Tks a bunch,
>>>>> Cristi Manole
>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>> For additional commands, e-mail: [EMAIL PROTECTED]
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
