Update to Prototype 1.6.1 RC 3 fixes all style problems with IE8, no need to fuss with the SCAL code.

I have posted a quick fix for the IE8 layout problem for scal.js. Specifically, there were 2 issues:

1) IE8 doesn't like attributes in Prototype's Element object instantiation (new Element()). This issue exists with Prototype 1.6.0.3 and previous.

2) Placing "//@" in the comments throws an syntax error in IE8. Adding a space before the @ (such as "// @") is OK.

Both of these changes have been implemented in the scal.js file I have uploaded to the Google group, so hopefully they will be committed to the respository soon.

In the mean time, you can download the scal.js file from:

http://www.submergedsolutions.com/lib/scal/scal.js

-Kris

Kris Hardy
Submerged Solutions LLC
kris@submergedsolutions.com
614-446-8733

Can you please be more specific with this bug fix. Ive went through scal.js and updated all places where a new element is created and changed adding the class name to the method stated above. Could someone please post a link to an updated scal.js file that is working? I think alot of people are having this problem since more and more IE8 browsers are showing up. Thank you for finding the fix for this. I just cant get it to work.

I'm sorry, all instructions of fix the problem are right. Everything works.

The calendar doesn't works in IE8. I've tried to change all functions New Element, but it didn't help. The situatuion got worse. The problem is that the header with Month, arrows of previous and next month and close button are displayed incorrect. Here's the screenshot of it: http://www.image123.net/898uaqg78g0upic.html
Does anybody can help, or just am I doing something wrong? Thanks.

Forgot to mention, but off course this goes for scalplanner.js also...

Ok,
Found the problem with IE8,
IE8 does not support creating new Elements in the manor:
new Element("a", {'class': 'carrot'});

so these constructs has to be rewritten to:
carrot = new Element("a");
carrot.addClassName('carrot');

takes a few minutes to do, but completely doable...

Hmm, seems like we got some problems with at least some of the styles, anyone got a quick fix for the iscal style header?