Sounds funny, but true. Yesterday while working for worldclockflake I just suffered this problem. You may reproduce this error as shown below

<script>
var dt = new Date();
alert(dt.getYear());
</script>

fortunately, IE is free from this prob.