Your company not moving to IE7 in a hurry?
The sysadmin type people at my work don’t want to move to IE7 probably until there is an SP1 release. While I understand their reluctance, it is frustrating developing for IE6 knowing that a better corporate SOE alternative exists! A lot of the leak issues we experience now will be minimised, and the speed improvements alone are a compelling reason to upgrade.
I hope Microsoft release a SP1 release soon.. What if they never do, and we have to wait until IE8!?
However, there are other issues.. Other internal/external web applications, that the organisation relies upon, will need to work with the new version, and I don’t think we will upgrade until that can be guaranteed.
Comments
Comment from tony petruzzi
Time: January 14, 2007, 6:01 am
I think the reason most companies won’t is because of the problem with popular firewalls and IE7. Take BlueCoat for instance:
Comment from Darryl Lyons
Time: January 14, 2007, 7:45 am
Yeah, the apps that we manage work fine, and in fact, even better. I think that sometimes you just have to take the plunge.
One of the other things is the interface. It has changed a fair bit, and some users will be confused by that. You can mitigate that risk by giving people side-by-side comparisons in the lead up time to deployment.
Comment from jackey
Time: July 11, 2007, 7:01 pm
When i use IE7 to develop,i fount a lot wrong style cause by css,but in ie6,it’s nothing.So from then,i never use ie7.
Comment from Justin Carter
Time: January 13, 2007, 10:52 pm
Usuaully the type of people that say “We’ll wait until SP1″ are the ones that really have no idea about the product to begin with, unfortunately.
Why wait until SP1? Is it broken? Are there vulnerabilities? Is a service pack going to drastically change the product from what already exists now? The answer to all those questions is a resounding: No.
There also aren’t a great amount of things that worked in IE6 that break in IE7. I work for a large government department which has many web apps developed centrally and regionally, and in the 10+ months that I’ve been using various IE7 builds and the last several months with the final build I have yet to find an issue with any of our systems (and believe me many are less than perfect). The main issue moving from IE6 to IE7 is where developers have used “CSS hacks” or selectors that have now been fixed in IE7 - if your apps aren’t CSS heavy (like those less than perfect ones I mentioned) then it’s likely that you’ll have no issues at all.
All it really boils down to is testing. Test things yourself. Begin some testing with other users in your office who are near by and that can report issues. But if that’s not your call to make then I guess you’re a bit stuck.
That said, I’m somewhat in the same boat as you, although I do have the option to move the region to IE7 if the need arises. My problem? Not enough hours in a day