I find it a bit strange that the DatePicker component has so obvious bugs
for IE. Don't the developers for this component ever test it in IE? The SSL
secure warnings in IE are a big problem, and it doesn't work for IE at all
in T4 (page doesn't load in browser, see other postings about this). If you
want to use it with T4, you'll have to patch the source...

Inge


On 1/18/06, Patrick Casey <[EMAIL PROTECTED]> wrote:
>
>
>         Isn't it in the jar? So unless you get the source I'm not sure you
> can change it conveniently. Even if you pull the .js out of the jar (it's
> plaintext) the bytecode for the .class will still load the .js out of the
> jar won't it?
>
>         --- Pat
>
> > -----Original Message-----
> > From: Chris Chiappone [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, January 18, 2006 2:13 PM
> > To: Tapestry users
> > Subject: Re: DatePicker and SSL in IE
> >
> > Where is the datepicker.js file located?  I need to make this
> modification
> > also.
> >
> > On 1/12/06, Rudolf Baloun <[EMAIL PROTECTED]> wrote:
> > > Nice! Big thx John Price.
> > >
> > > I fixed the bug, with modifing following line in Datepicker.js:
> > >
> > > from
> > > underDiv.innerHTML = "<iframe width=\"100%\" height=\"100%\"
> > > frameborder=\"0\"></iframe>";
> > > to
> > > underDiv.innerHTML = "<iframe *src=\"/img/empty.gif\"* width=\"100%\"
> > > height=\"100%\" frameborder=\"0\"></iframe>";
> > >
> > > "/img/empty.gif" is a 1x1 pixel emty picture.
> > >
> > >
> > >
> > >
> > > Prince John, Bedag wrote:
> > >
> > > >Hi,
> > > >
> > > >The problem is the lack of a src attribute in the iframe in
> > > >datepicker.js. IE interprets this as an insecure link (as it does
> > > >about:blank...) We got round this by hacking the script (which we
> > needed
> > > >to do anyway, as it happens) to add a src attribute.
> > > >
> > > > Best wishes
> > > >
> > > >John
> > > >
> > > >-----Original Message-----
> > > >From: Rudolf Baloun [mailto:[EMAIL PROTECTED]
> > > >Sent: Thursday, January 12, 2006 9:06 AM
> > > >To: Tapestry users
> > > >Subject: Re: DatePicker and SSL in IE
> > > >
> > > >I updated to Tapestry 4.0 Stable, but its still NOT work...
> > > >
> > > >Rudolf Baloun wrote:
> > > >
> > > >
> > > >
> > > >>Hi,
> > > >>
> > > >>i use Tapestry 4.0 Beta 13.
> > > >>After patching some Bugs, the Datepicker works good.
> > > >>I still got one problem with the DatePicker:
> > > >>When i use SSL (HTTPS) the DatePicker uses "unsave" Code.
> > > >>The Internet Explorer warns me, that the Datepicker uses unsecure
> > > >>
> > > >>
> > > >Code.
> > > >
> > > >
> > > >>The Firefox doesnot warn me.
> > > >>
> > > >>Is this an IE Bug or does the Datepicker not work with ssl?
> > > >>Does someone know, how i can use the Datepicker with ssl and IE?
> > > >>
> > > >>Best Regrats
> > > >>
> > > >>Rudolf B.
> > > >>
> > > >>
> > >
> >>---------------------------------------------------------------------
> > > >>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]
> > > >
> > > >
> > > >---------------------------------------------------------------------
> > > >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]
> > >
> > >
> >
> >
> > --
> > ~chris
> >
> > ---------------------------------------------------------------------
> > 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]
>
>

Reply via email to