It's a problem, what do you develop for, which standards do you use??
Courselab is using mature but complex technology and it has to be optimised to work on something, at the time IE was the dominant browser engine and like it or not it still is. This means 2.4 was biased towards 100% function on IE and hopefully a graceful failure on mozilla or webkit. As these engines have diverged more the faults sometimes get worse in one area or improve in another.
Chrome does some quite naughty things to increase it's users perceptions of speed, usually it's OK other times not.
So the dev team were chasing a moving target on any compatibility.
Now if we are talking 2.4 you have to remember that (a) it's free (b) it's still probably the best free tool you are going to find (c) IT'S FREE and (d) it is a few years old now and the world moves relentlessly on. It is really unlikely that you'll see any change to 2.4 (see above a-d) however people like Barend and other users do tinker under the hood with the JS and XML code base and may come up with hints or tips to increase cross compatibility, depends if we have the time as we do have real jobs and lives!
I can't comment on the 2.65 version but I understand it was better on non IE platforms.
I can comment on 2.7 which has had a lot of work put into it on cross browser compatibility. It looks like it has worked too.
I mainly use FF and I've seen no problems with the 10915 beta build which I think looks like the full release candidate.
If you're affiliated with a commercial organisation, as many people here are, then get it when it comes out should bring a smile to your face ;)
It's a problem, what do you develop for, which standards do you use??
Courselab is using mature but complex technology and it has to be optimised to work on something, at the time IE was the dominant browser engine and like it or not it still is. This means 2.4 was biased towards 100% function on IE and hopefully a graceful failure on mozilla or webkit. As these engines have diverged more the faults sometimes get worse in one area or improve in another.
Chrome does some quite naughty things to increase it's users perceptions of speed, usually it's OK other times not.
So the dev team were chasing a moving target on any compatibility.
Now if we are talking 2.4 you have to remember that (a) it's free (b) it's still probably the best free tool you are going to find (c) IT'S FREE and (d) it is a few years old now and the world moves relentlessly on. It is really unlikely that you'll see any change to 2.4 (see above a-d) however people like Barend and other users do tinker under the hood with the JS and XML code base and may come up with hints or tips to increase cross compatibility, depends if we have the time as we do have real jobs and lives!
I can't comment on the 2.65 version but I understand it was better on non IE platforms.
I can comment on 2.7 which has had a lot of work put into it on cross browser compatibility. It looks like it has worked too.
I mainly use FF and I've seen no problems with the 10915 beta build which I think looks like the full release candidate.
If you're affiliated with a commercial organisation, as many people here are, then get it when it comes out should bring a smile to your face ;)
