Details

Description

This concerns all beta versions of 4.0, even including tonight's CVS HEAD, which is supposed to be Beta-4.

Whenever I use an unmatched <p>, or even a <p/>, without an explicit </p> in a page with a DatePicker, I get a really strange error from MSIE, in that MSIE pops up the error dialog "Operation aborted." It does NOT happen when I match the <p> tag with a </p> or use other components, such as TextField.

Howard M. Lewis Ship
added a comment - 24/Aug/05 08:02 Yep, this seems to happen. Only in IE. Once it happens, IE fails to send further requests to the server (I see no requests in the NCSA log). Not sure how to proceed!

As far as I tracked down this issue the problem is that the IE really dislikes the <script> of the DatePicker if it's not a top level element (directly under the body). I got the same 'operation aborted' message.
The only solution that worked was to open and close all elements properly. I even had a problem with a <div/> tag I had to change to <div></div> because the IE was too stupid to recognize the first one as closed. Maybe it's the same problem here. I'd try a <p></p>. In such a scenario I found the IE-Webdeveloper Toolbars DOM-Inspector to be a great help.

Mario Siegenthaler
added a comment - 05/Nov/05 22:32 As far as I tracked down this issue the problem is that the IE really dislikes the <script> of the DatePicker if it's not a top level element (directly under the body). I got the same 'operation aborted' message.
The only solution that worked was to open and close all elements properly. I even had a problem with a <div/> tag I had to change to <div></div> because the IE was too stupid to recognize the first one as closed. Maybe it's the same problem here. I'd try a <p></p>. In such a scenario I found the IE-Webdeveloper Toolbars DOM-Inspector to be a great help.