Slashdot Mirror
IE7 Compatibility a Developer Nightmare
yavori writes "Internet Explorer 7 has kicked in at last on all MS Windows OS running PCs because of the fact M$ decided to force it's users to migrate through update. In fact this has started a IE7 Web Developers Nightmare. The article actually explains that most of the small company B2C sites may just fall from grace because of IE7 incompatibility. One of the coolest thing IE7 is unable to do is actually processing form data when clicked on an INPUT field of TYPE IMG... which is pretty uncool for those using entire payment processes with such INPUT fields."
It would be nice to see examples of failing code, for instance. I've not tried it myself yet. The author's English skills leave a lot to be desired, to the point of making his complaints a bit vague.
The upside to this is that the same "forced" upgrade procedure MS are using to roll out IE7 can also be used to roll out bigfixes without user intervention, if IE7 was originally installed transparently anyway.
Anyway, I can't say it a big surprise that IE7 has its own foibles. IE6 was also a developer's nightmare, with the DOM and JS environment behaving differently from Firefox, Opera etc, so it's just another workaround. I'm only disappointed that Microsoft didn't make more of an effort to bring it inline with the competition so we could avoid yet another set of JS and CSS hacks. It's not like they have limited resources!
sig:- (wit >= sarcasm)
And the MOST killer thing was the DISability of IE to submit data through "input type img"
Maybe I'm not understanding what the claim is, but it's easy to demonstrate that this is not true. I just tried with IE7 to submit data on a form that uses an input type of image and see that it works fine.
This article has almost no information and it seems the only reason it was posted here is to stir up anti-Microsoft antagonism. (Now someone will say, "You must be new here.") :-)
In my experience, IE7 is much better at supporting standards than IE6. A huge improvement in CSS support, so that now as I design in Firefox 2.0 and occasionally verify things in IE7, I see that they are very, very close. Most of what I'm doing is working with WordPress blogs so it's very possible I'm not using things that are now broken, but if anything Microsoft should be given some credit for improving their browser.
There's plenty of reason to not like Microsoft, but this article doesn't supply much (if any) ammunition, and it doesn't do the free software crowd much of a service to engage in our own unsupported FUD.
As some have pointed out, this appears to be an incomprehensible rant. The "article" referenced says little and backs up that little with less.
I also notice the "submitter" seems to be the same person as the blogger for the article. Not saying this shouldn't happen, but this usually shouldn't happen... If it's good enough to get "published", it's good enough to be published by someone other than the author.
It still won't parse the DOM. Stuff that is simple in Firefox, will never work in IE 7.0. I gave up trying to get some features to work.
For instance, I have this js based terminal emulator. I don't want to edit that package, but just use js to read some fields. This is sexy in Firefox, but no chance in IE 7.0.
if (document.Form1.tsprog.value == 'fibfm' || document.Form1.tsprog.value == 'FIBFM'){
var pwrap = document.getElementById("pbsiwrap");
var cells = pbsiwrap.getElementsByTagName("span");
var item = cells[12].textContent;
document.getElementById ("headspot").innerHTML = '';
}
Developers now have to support IE5, 6 and 7.
No, not necessarily. Web Developers are advised to test against all browsers with more than a 3% market share for their site. If your site has 3% share of IE 5, 6, and 7, then you've got your work cut out for you. Most others don't have that problem.
Just because some academics came up with a "standard" doesn't mean there's a law that says that everyone needs to follow it. They should be called "suggestions".
The wonderful thing about standards, when done correctly, is that everyone can support the standard and get essentially the same result.
In all honestly, if your website can't function fine with the minor variations between browsers, then you've got a bad design. (And let's not even get into how bad your site will look in mobile devices, or without images, or for the blind.)
Oh really? I still have IE6, although I never use it except when forced to. Who are these people who have been "forced" to upgrade?
We have a webapp that was built for our call centers. It started out in IE 4 and then later we did some updates for IE5. IE6 came out and there were a few JavaScript things to fix-up (nothing huge) but by then we had ditched almost all of the non-standard code and moved from table layout to pure CSS layout. When IE7 came out we didn't need to make a single change to the JavaScript, CSS, or HTML. All 200+ pages just work.
Everyone was worried that because of our choices and how heavily we rely on CSS and JavaScript that we would be in for a nightmare. Luckily, not so. However, two of the products we purchased for time tracking and for defect reporting both DIE because they have user agent checks built into their javascript. When they run into the unknown IE7 string they just chirp back a warning message and don't even try to load up. How many times do web developers need to be told "browser detection is bad use object/feature detection" before they'll get it.
I don't think that I've had any problem with any of the normal sites that I use when using IE7 over the last couple of months (banking, news, mail, social). I get the feeling that the author of this article just doesn't know what he's talking about.
"Do not be swept up in the momentum of mediocrity." - anon