Look at the top of the screen. File Edit etc. etc. Help Click help and then About ... the version number is on that pop up.
But, but :(...My work computer has IE 6.0. And I don't think I'm allowed to change it. How will be able to procrastinate at work if I can't get on WorldSims and look at the forums? ::sniff sniff:: WAAAH!!!!!!!!!!:sob:
I was thinking the same thing. There isn't anyway for me to download either IE7 or Firefox at work because I don't have admin privileges on this computer of course. At home I'm covered, but here it just sucks. I suppose that means I just have to focus more on work huh...
OK, I think I'm missing something here...Are we talking that WorldSims is going to phase out support for some Browsers? Which ones?? I'm in the same boat as many others in that I can not change the browser I use at work. ______ Oh - OK...Just spotted the anouncement. Yes, this will be a problem for me as I do most of my World Simming at work, where we use IE6. I have no way of changing that... :(
Oh, I wouldn't worry too much, Meg. I doubt that the changes would be so drastic that you won't be able to use the forums. The only major effect is that you would notice the forum pages look a lot different between when you access with IE6 and when you access with IE7. Ending support does mean the site will no longer work with older browsers, it just means that every time a change is made to the site Josh and his team will no longer bother to test that the site looks the same in all browsers; most times the difference will be non-existent or negligible, at other times it'll be huge. But in all cases it would be an exceptional case where the site could not be read at all.
Actually the changes will be pretty big. Basically, aspects of the site will not render in older browsers. You can still utilize the forums and stuff, but we won't guarantee it will work as we want it to.
Heh. Well technically it was referring to your second statement more than the first. We'll still test it some, but we're not gonna bother coding in corrections to make sure a site fully works or not with our code. And the changes will be significant. In some instances, the site won't appear at all. So technically not negligible I'll design a quick contingency plan to allow for older browsers to use the site; but unfortunately it won't look as pretty or be able to utilize the site to the fullest.
Urr ... I did actually mean to say: If that's what you meant. I recently had a fairly massive problem of compliance between FF2/IE7 and IE6. The groovy gang at the Yahoo CSS Style group couldn't fix it and neither could I. All the page elements were visible in the older browser ... just not in the right order/position. In the end the client didn't notice anyway so I left it .... Well I was doing it on the cheap. What I really intended to say was this. It is unlikely that changes to a website would make its text contents become invisible to an older browser.
...I dunno if I like the idea of the switch. I mean it doesn't really affect me, as I sit here and type this on my Mac with Safari... but maybe there's a reason that there's a lot of people still using IE6. Personally, I've used IE7 and hate it. I don't really think the expectation of users to install Firefox is reasonable, either, especially to those who have acclimated themselves to the Windows based browser. Finally, as a minority, I'm feeling a little discriminated against. Every self-respecting Mac user knows that Firefox is better than IE but worse than Safari on Mac. You should consider offering support for Safari as well--it's the way of the future p)
If you want to buy me a Powerbook so I can do development for Safari, then I will offer support. But it's sort of hard to offer official support for Safari when I don't have the tools to develop on it.
There used to be a project which would provide a screen shot of a url as Safari/Mac would see it. Of course it wasn't a full test, but it helped to assure that crucial CSS elements were at least working correctly. Found it: http://www.danvine.com/icapture/
I noticed after I'd posted the link. It used to work. I imagine it costs a fair bit to maintain. I suppose Dan has to take it offline now and then to preserve his server sanity.