Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×

IE7 Compatibility a Developer Nightmare 416

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."
This discussion has been archived. No new comments can be posted.

IE7 Compatibility a Developer Nightmare

Comments Filter:
  • by djkitsch ( 576853 ) on Sunday January 07, 2007 @01:31PM (#17498522)
    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!

  • Bah (Score:5, Interesting)

    by F452 ( 97091 ) * on Sunday January 07, 2007 @01:31PM (#17498526)

    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.

  • by yagu ( 721525 ) * <{yayagu} {at} {gmail.com}> on Sunday January 07, 2007 @01:33PM (#17498536) Journal

    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.

  • This is so True (Score:5, Interesting)

    by Slipgrid ( 938571 ) on Sunday January 07, 2007 @01:39PM (#17498608) Homepage Journal
    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 = '';
    }
  • by Planesdragon ( 210349 ) <<su.enotsleetseltsac> <ta> <todhsals>> on Sunday January 07, 2007 @01:50PM (#17498718) Homepage Journal
    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.)
  • Forced Upgrade? (Score:5, Interesting)

    by rudy_wayne ( 414635 ) on Sunday January 07, 2007 @02:18PM (#17498942)
    "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."

    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?

  • Re:This is so True (Score:5, Interesting)

    by mollymoo ( 202721 ) on Sunday January 07, 2007 @02:20PM (#17498964) Journal
    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.

    The document.FormName.InputName.value form is not part of W3C standards. Try document.forms["FormName"].InputName.value and see if valid code works.

    I would hope that with an up-to-date doctype declaration (strict rather than quirks mode) Firefox would barf on that invalid code too.

  • by nhavar ( 115351 ) on Sunday January 07, 2007 @03:40PM (#17499722) Homepage
    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.

  • by Anonymous Coward on Sunday January 07, 2007 @04:22PM (#17500078)
    First, I'm not an IE user and I'm not defending it, but...
    Using images instead of input type="submit" is a usability flaw. I also believe if you use it you will use your WCAG compliance.
  • by MtHuurne ( 602934 ) on Sunday January 07, 2007 @04:24PM (#17500094) Homepage
    Our webapp is a bit smaller (a few dozen pages), but our experience is similar to what you describe. Our XHTML, CSS and JavaScript which already worked on IE6, Firefox, Opera and Konqueror also worked on IE7 without problems.

    In my opinion IE6 Compatibility is a Developer Nightmare and once those installations have been replaced by either IE7 or a non-Microsoft browser my life as a webapp developer will be a lot easier.
  • by Pieroxy ( 222434 ) on Sunday January 07, 2007 @05:53PM (#17500968) Homepage
    If any other news outlet

    Can you honestly tell me that you know at least ONE news outlet for which facts matter? I live in France and used to live in the U.S. and I am still waiting for one.
  • by KWTm ( 808824 ) on Sunday January 07, 2007 @07:49PM (#17501976) Journal
    Much as I despise Microsoft, fixing IE7's rendering (at least partially) was a good move. Not only did it move closer toward the standard, but it *broke* a bazillion web pages that were non-compliant but displayed as intended on IE6 or earlier.

    Previously, if you told those lazy web developricks, "Hey, your web site doesn't display properly on Firefox, which is a whopping 4% of the market!" then they would answer, "Works fine with my computer --your Firefox must be broken." Well, guess what? Now it doesn't display properly on the latest IE either, and with Microsoft forcing IE7 down everyone's throats, it's not just going to be some insignificant minority who complain. More considerate developers who slave away at making those IE-specific adjustments can now say, "You need to get the latest version of IE in order for the web site to work," and then wash their hands of maintaining any more IE6-or-earlier hacks. IE7 will have a beneficial effect even for those of us who never use MS products, because it will have a profound effect on the WWWeb.

    And those poorly designed websites mentioned in TFA, which will have to be redone to be IE7 compatible thus driving small businesses to bankruptcy? Well, cry me a river. Reminds me of the early days of the web when people just cut'n'pasted other web pages to cobble together their own Frankenstein[1] of a web site, which displayed perfectly on Netscape 3.1 but whose source code was an abomination.

    You know when the Slashdot community bitches about Microsoft, and some MS supporter always asks, "You guys are never satisfied! What's Microsoft gotta do to make you admit that they are doing something *good*"? Well, fixing IE7 numbers among the answers (right under "Open up the MS Word format"). Keep up the good work, Microsoft, and someday your product might be as good as Firefox.

    _____
    [1] Yeah, I know Frankenstein is the creator of the monster, not the monster itself, but I'm using the term in the popular culture sense.
  • by Schraegstrichpunkt ( 931443 ) on Monday January 08, 2007 @12:41AM (#17504338) Homepage

    Here's a suggestion: Look at your site in Firefox before trumpeting how great you are on web standards.

    Or, at a minimum, use browsershots.org [browsershots.org].

Remember, UNIX spelled backwards is XINU. -- Mt.

Working...