Hi!
This solved my problem. Thanks for the reply Schabek (and the
contributions from the others)!
Here is what I've done:
* Replace (delete/paste) the writeInitializationScript() method in
the PageRenderSupportImpl class (as proposed at
http://issues.apache.org/jira/browse/TAPESTRY-788).
* Rebuild the Tapestry JAR targets from the sources (as explained at
http://wiki.apache.org/jakarta-tapestry/BuildingTapestry).
* Copy the JAR targets into my application's dependencies folder
(overwriting the default ones from Tapestry 4.0)
If this can help anyone else...
/Martin
Schabek Łukasz wrote:
It is an IE bug only, reported and solved here:
http://issues.apache.org/jira/browse/TAPESTRY-788
Just replace writeInitializationScript method.
-----Original Message-----
From: Martin Carel [mailto:[EMAIL PROTECTED]
Sent: Monday, January 30, 2006 5:02 PM
To: Tapestry users
Subject: DatePicker in IE: operation aborted
Hi !
I have issues with the DatePicker component using Tap4. Works fine in
Firefox, but I got the "operation aborted" popup in IE, which prevents from
showing the page. Thus, this is critical for our application.
When I have only the DatePicker component in my page, it works fine. But
when I put my border component (rendering headers and footers, which
includes some JS), that's when the problem arises. I cannot guarantee the JS
in those headers/footers is error-free (and I suspect the DatePicker
component is sensitive to JS errors on the same page - for example more than
one </body> tags) and I cannot afford to change any of the code generated by
this border component.
--
I have investigated the problem in the the mailing list and in JIRA
(https://issues.apache.org/jira/browse/TAPESTRY).
http://issues.apache.org/jira/browse/TAPESTRY-173
This absolute/relative position issue is not my problem, because when I have
my DatePicker component at the top level (directly under <body>), but with
the border component, I still have the problem.
http://issues.apache.org/jira/browse/TAPESTRY-222
I added the catch clause in the getPoint() function of DatePicker.js in
tapestry-4.0.jar, but this didn't change anything (even if it is said to be
solved in Tap4).
http://issues.apache.org/jira/browse/TAPESTRY-233
I have removed the call to "this._calDiv.focus()" in DatePicker.js in
tapestry-4.0.jar, but this didn't change anything (even if it is said to be
solved in Tap4).
As for the mailing list, there has been some issues with the DatePicker
component and SSL (a missing src attribute), but this is not exactly my
problem.
Any hints would be appreciated.
/Martin
---------------------------------------------------------------------
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]
