Slashdot Mirror


IE7 Bug Reports Flooding In

the JoshMeister writes "According to ZDNet, bug reports are already flooding in for Microsoft's new Internet Explorer 7 Beta 2 Preview. Specific issues include the possibility of arbitrary code execution as well as incompatibilities with McAfee Security Center, anti-spyware programs, and online banking sites." From the article: "... browser testers may already be at risk, according to security researcher Tom Ferris. Late Tuesday, Ferris released details of a potential security flaw in IE 7. An attacker could exploit the flaw by crafting a special Web page that could be used to crash the browser or gain complete control of a vulnerable system, Ferris said in an advisory on his Web site. Microsoft had no immediate comment on Ferris' alert."

52 of 259 comments (clear)

  1. Duh! by sparkydevil · · Score: 5, Insightful

    Of course it's got bugs -- it's a beta!

    1. Re:Duh! by dotpavan · · Score: 3, Insightful

      its a preview to the beta 2! wait for the beta 11 preview 46, its better

    2. Re:Duh! by Anonymous Coward · · Score: 2, Insightful

      Well yes it is a beta and for that its not expected to be perfect. However this is for a product that is supposed to be secure by design, not by patching a million leaks like in the previous release of IE. I find it quite unacceptable to be finding major security issues so quickly.

    3. Re:Duh! by TheComputerMutt.ca · · Score: 2, Insightful

      Google's beta products do a little better than this, no?

    4. Re:Duh! by tassii · · Score: 2, Interesting

      Of course it's got bugs -- it's a beta!

      I think the notable part is its the same bugs as IE 4 had.. and IE 5... and IE 6...

      --
      "I drank what?" - Socrates
    5. Re:Duh! by plague3106 · · Score: 3, Insightful

      Why would you use a beta for production work at all?

    6. Re:Duh! by EntropyEngine · · Score: 2, Insightful

      I just don't really see this as being too news-worthy.

      What would be news-worthy is if Microsoft completely ignored all of the bug reports and went Golden Master tomorrow...

    7. Re:Duh! by Imsdal · · Score: 2, Funny

      Sure. After three years in beta, most of the bugs have usually been removed.

    8. Re:Duh! by Junior+J.+Junior+III · · Score: 4, Insightful

      That's what I was going to say, bug reports flooding in are a sign of a successful beta test. I wonder how many of them Microsoft will actually be fixing, though... that's kindof the whole point of it all.

      --
      You see? You see? Your stupid minds! Stupid! Stupid!
    9. Re:Duh! by walt-sjc · · Score: 2, Informative

      So what ever happened to "trustworthy computing"? I believe the userbase would really like to see MS redesign IE from the ground up, much like what happened to netscape / mozilla. While it's no small effort, we are talking Microsoft here - it's not a cost issue. Perpetuating a design that has NEVER emphasized security just seems like the wrong thing to do - especially when it's "an integral part of the operating system" (as MS claims.)

    10. Re:Duh! by MobileTatsu-NJG · · Score: 2

      "Google's beta products do a little better than this, no?"

      Google has the benefit of most of the code running on their own hardware. A better example would have been the FireFox team, but even then it would have to be admitted that writing a good browser is pretty fucking hard.

      --

      "I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)

  2. Wow by saboola · · Score: 4, Funny

    A beta of a Microsoft product has bugs? Color me surprised!

    1. Re:Wow by ucahg · · Score: 3, Insightful

      A beta of anything better have bugs. Otherwise the testers aren't finding them because they are most certainly there.

      I don't even see how this is a news-worthy... it's a beta!

  3. Bug reports already? by VJTod · · Score: 3, Insightful

    It's beta software. Of course there will be bugs. The public B2 is much better than the leaked B2 which was still better than B1.

    Taken with grain of salt... it's still beta.

  4. good! by steve.m · · Score: 4, Insightful

    sounds like a productive beta test. end users finding lots of bugs.

    (anyone who would use it - or anything else beta - in a production environment is insane)

  5. Security is Job 1? by InfinityWpi · · Score: 2, Funny

    This just goes to prove that Microsoft's newfound 'dedication to security' and focus on writing code with less bugs in it is just a pure crock of doodie. Obviously, if they opened their source and let us all look at it, we'd be glad to help them find and iron out all the bugs by releasing several dozen exploits into the wild at the same time. My god, if the beta's this bad, how bad will the finished product be when they've finished adding features? ... um, my sarcasm tag is on, right?

    1. Re:Security is Job 1? by varmittang · · Score: 2, Insightful

      It just makes you wonder if their new programming process MS has is better or worst than what it was before, and how it is letting these bugs get though. Was the product really not finished, yes I know its beta but most betas are at least close enough to finish that the programmers are looking for the obscure bugs, not ones that are just flat out sitting in the open like they are with IE 7. Is it the Alpha stage just slapped with a beta name so people will stop hounding them for IE 7.

      --
      -----BEGIN PGP SIGNATURE-----
      12345
      -----END PGP SIGNATURE-----
    2. Re:Security is Job 1? by szembek · · Score: 2, Insightful

      I think you're missing the point that this is a beta test, the point of it is to find the bugs that are inevitably in any program. It is a good thing that they are being flooded with bug reports, because they can now see what needs to be fixed before releasing it. Of course I am not saying the final release will be bug free, but hopefully this preview will be successful enough to help Microsoft create a stable release.

      --
      nothing
    3. Re:Security is Job 1? by FireFury03 · · Score: 2, Interesting

      most betas are at least close enough to finish that the programmers are looking for the obscure bugs

      What surprised me about beta 1 was that they hadn't even finished implementing features that were already on the final product's feature list. Actually, it seemed that they hadn't actually finished deciding what was going on the feature list.

      Most people would consider that development stage to be alpha - beta is where you have finished implementing the feature list and you are now after feedback from the customers on bugs, user interface and what extra features they think need to be implemented which weren't on the feature list. I.e. a beta release should fulfill the original specification, albeit still needing some bugfixes.

  6. This a good thing by Beelub · · Score: 5, Insightful
    Getting bug reports on beta software is good. That's why it's released as beta.

    Why is this front page, unless it's just the usual knee-jerk, let's-find-something-bad-to-say-about-Microsoft thing that makes Slashdot less than useful for info about anything about Microsoft.

    Yeesh.

    1. Re:This a good thing by 99BottlesOfBeerInMyF · · Score: 4, Insightful

      Why is this front page

      This is on the front page for a number of reasons. First, it is somewhat indicative of the quality of the new software MS is planning to release. Yes, betas will have bugs, but no comment has been made about the remote exploit from MS, nor about the myriad failures to implement CSS properly. The number of bugs found in such a small time, is a meaningful metric and of interest to people here. It indicates to many of us, that the final version is still unlikely to properly implement the spec and that whatever new security practices MS is employing are probably not working to stop vulnerabilities. (Gee, big surprise.) The number of incompatibilities with current banking and other Websites is a useful indication to how much work the Web designers among us are likely to have ahead of us.

      Second, because of the design of Windows and IE you can either install this beta for testing, or you can install the current IE, but not both. This means a number of people will install the beta, but end up also using it as an everyday browser, since they don't want to be constantly installing and uninstalling it for testing. Thus, security concerns with this beta may actually be a real concern. Those among us working to secure networks may want to account for this by restricting use of this browser for the time being.

      Finally, the number of bug reports is a useful metric for gauging interest in the product, which is also of concern to people here.

  7. Story is inaccurate... by Manip · · Score: 5, Interesting

    Calling Tom Ferris a "Security Researcher" is like calling Bill Gates a programmer... He is more a 'Robert Scoble' character. And his discovery of arbitrary code execution is incorrect as per the link: http://blogs.msdn.com/ie/archive/2006/02/01/522682 .aspx

    The guy is not a professional anything, I mean he lists workarounds as 'Firefox'; which just shows how little he understands the security field which he claims to work in (A workaround should be a way to fix or bypass the bug, not a blind pointer at some random other product, even the Linux Security guys know that).

  8. Bug identification & research for a beta relea by digitaldc · · Score: 4, Funny

    Look at the bright side, now we know what Ferris does on his days off.

    --
    He who knows best knows how little he knows. - Thomas Jefferson
  9. Not surprised by the bugs... by ripbruger · · Score: 3, Informative

    ...but I downloaded and installed and uninstalled this thing last night. Still seems there are loads of CSS problems in it (couldn't get a navigation menu to work but using :hover pseudo-class). It'll be interesting to see what MS comes up with on this one. It'll be nice to actually have a capable version of IE to test pages against.

    --
    I can't spell ripburger
  10. It's.. Beta? by PhrostyMcByte · · Score: 4, Insightful

    How is this news? Betas are there for finding bugs. If you don't want to risk more than the usual, how about just not using it?

    The past builds were also riddled with bugs, and the IE developers are very involved with testers to fix them. It's not like they're just sitting with their hands over their ears yelling "LA LA LA LA I can't hear you!"

    1. Re:It's.. Beta? by RangerRick98 · · Score: 2, Insightful

      It'd be one thing if I could have IE 6 and IE 7 installed on the same install of Windows so that I could run them side-by-side. Then I could test stuff in IE 7 but still do the bulk of my Internet browsing with IE 6 which (theoretically) doesn't have these flaws.

      Of course, in reality, I use Firefox for everything, so it's a moot point for me, but nevertheless it doesn't make sense to me that someone would release a beta product and have it install over top of a production product.

      --
      "You're older than you've ever been, and now you're even older."
    2. Re:It's.. Beta? by Anonymous Coward · · Score: 2, Informative

      (via Jon Galloway) Sure, you knew IE7 Beta 1 was up on MDSN, but you don't have a free machine to test it on. Can't install it on your main work machine, because you can't afford to mess it up... plus, you need to be testing your work against IE 6, right? You thought about setting up a Virtual PC image, but it seemed like too much trouble for a Beta 1. Still, it would be nice to click around in it for a few minutes here and there... Fret no more! IE has a secret standalone mode which lets you run multiple versions side by side (thanks to Joe Maddalone for figuring this out). It's pretty simple: Download the IE7 Beta 1 Install from MSDN Open the install file with WinRAR (yep, it's an EXE, but it's a self extracting EXE) and extract them to a folder. Alternatively, you can just run the EXE, make a copy of the files which are extracted in the first step, and cancel the install. I was too chicken to do this on my work computer. Look in the folder you extracted to for the file SHLWAPI.DLL. Delete this file. Create a new text file in the folder, then rename it to IEXPLORE.exe.local. That's it. The .local file in the folder tells the IExplore.exe instance to run in local mode, which means it won't mess with your IE6 settings, registry, etc. It sounds complicated, but it takes less than 10 minutes and it goes just great with your Friday morning coffee. Of course, you can help your friends at work (who also have MDSN subscriptions, of course) by zipping the folder and sharing it with them so they don't have to go through this crazy mumbo jumbo. Incidentally, there are archives of old IE versions converted to standalone mode over at browsers.evolt.org and at skyzyx.com. C'mon, spend a day with IE3 for old time's sake!

  11. More annoying than the bugs.. by chou+oishii · · Score: 5, Interesting

    ..are the way it: a) Requires you to validate windows to install, b) Requires a reboot, and c) Actually attempts to pass off things like tabbed browsing and a search bar as innovative (really, take a look at the "demo" they bring you to when you first install it).

    I'm not asking them to spend money advertising the fact that they're way behind the curve on browsers, just to stop lying to me.

    1. Re:More annoying than the bugs.. by Psiren · · Score: 2, Insightful

      a) Requires you to validate windows to install,

      I personally don't see why this is a problem, but then I'm one of those strange people that happens to agree with the notion of paying for commercial software.

      b) Requires a reboot,

      Well, it's the usual tight integration with Windows, so I expected as much. Yeah, it's a bit of a pain, but if you're prepared to install a piece of beta software on your machine, rebooting it is hardly an issue, is it?

      c) Actually attempts to pass off things like tabbed browsing and a search bar as innovative

      Well, it is, for Explorer. That's just marketing anyway, it's nothing to do with the quality of the product, which is what most of us devlopers are interested in.

    2. Re:More annoying than the bugs.. by bmajik · · Score: 3, Insightful

      Requires you to validate windows to install

      Ok, this doesn't buy the customer much, but is it really all that big of a pain? Do you just conceptually object to Microsoft asking "is that a valid Windows you're using?"

      Requires a reboot

      I am not thrilled about this but given the wedding of the browser rendering component and the rest of the user experience ("OS"), i can't say i am surprised. You have to reboot after uninstalling it also, by the way :)

      Actually attempts to pass off things like tabbed browsing and a search bar as innovative (really, take a look at the "demo" they bring you to when you first install it).

      Consider part of the target market for IE7: People that are happy enough with the features of IE6 that they haven't bothered looking at Firefox yet. For them, tabbed browsing and a search bar are new and innovative. These are things that everyone will potentially benefit from but not all people will seek out and discover by themselves.

      Part of the reason my grandfather uses a computer at a public library to do web surfing and write email is because Microsoft brings "cool stuff" away from the realm of the early adopter and puts it in the hands of everyone.

      --
      My opinions are my own, and do not necessarily represent those of my employer.
    3. Re:More annoying than the bugs.. by DrSkwid · · Score: 2, Insightful

      > take a look at the "demo" they bring you to when you first install it

      where can I download the OpenBSD version ?

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    4. Re:More annoying than the bugs.. by ChaosDiscord · · Score: 2, Interesting
      I am not thrilled about this but given the wedding of the browser rendering component and the rest of the user experience ("OS"), i can't say i am surprised.

      While not surprising, it's still crap.

      The core flaw is that under Windows you can't delete a file that is in use. The accepted solution is to set up a little script to run on reboot that deletes the file and replaces it with the new version. That's sad and stupid.

      The Unix solution allowing you to delete an in use file solves the problem. It has its own weaknesses (as long as any process holds a file open, it chews up disk space), but at least you can upgrade even low level libraries (which is all the IE libraries are) without a reboot.

  12. So let me get this straight .... by Brian+McCoy · · Score: 4, Informative

    people are claiming that a Preview Release ,not even a full beta yet, has bugs? Just wondering what these industry leading geniuses thought they were getting with a preview release? I have been using IE7 for a couple months now, my work provides me with a Technet Plus subscription, and I have had some issues. In most, if not all cases, I have been able to work around them and still rely heavily on Firefox. I will say that Microsoft has finally added some much needed functionality to their browser such as tabbed browsing and keyboard shortcuts which are exactly the same as Firefox's (coincidence, I think not). I guess my point is it's a preview release, it's not perfect and it has bugs, by using beta software you are agreeing to help solve some of the problems before final release, and there will be problems. Just my two cents worth.

    --
    You must learn to be still in the midst of activity and to be vibrantly alive in repose. -Indira Gandhi
  13. Treat IE 7 as IE 6? by Pascal+Sartoretti · · Score: 5, Interesting

    The problem for Microsoft is that many web applications use the following logic:

    if (browser is Internet Explorer) then

    emit HTML code that works around the numerous rendering bugs of IE

    else (Mozilla, Netscape, Opera)

    emit standards-compliant HTML code

    With this kind of (flawed) logic, IE 7 will often be identified as IE, and hence be provided with IE 6-specific HTML code, whereas it should have been sent "correct" HTML code. The result may be, well, interesting :-)

    I really don't see what Microsoft can do against this. They can't expect millions of web sites to be updated overnight just to support IE 7.

    1. Re:Treat IE 7 as IE 6? by kawika · · Score: 4, Insightful

      Don't let Microsoft off the hook that easily. Most of the problems I've seen with this IE7 beta aren't the "we messed up the implementation" variety. They are the "we still don't support all of CSS" variety.

      Microsoft has eliminated several bugs that made it easy to identify IE6 and apply hacks to the CSS. For example, the "* html" selector let you apply CSS rules just for IE because it's ignored by standards-compliant browsers. Now IE7 ignores that too. However, the need for hacks is still there. IE7 still does not implement several important CSS features that necessitated the hacks in the first place, such as min-height.

      If Microsoft were to decide that this beta was "close enough" or even if it fixes just the minimum number of things to keep major sites from breaking, that's not going to help. Designers will end up needing an entirely different set of hacks to make up for the fact that IE7 is *still* not a complete CSS2 implementation.

  14. So what if it's a beta? by SpiritGod21 · · Score: 2, Informative

    OK, yeah, I got the point. It's a beta and betas will have bugs. But this isn't IE 1.0 Beta. This is freaking IE 7, and while it's a beta, you'd figure they'd have gotten at least some of these things straightened out in the past 6 versions. I'm not so much frustrated that a beta has bugs, but that even into version 7 they're still having huge problems and potential exploits.

  15. Nasty security flaw that Microsoft missed by OwlWhacker · · Score: 3, Insightful

    I was about to post something about bugs being natrual in almost all beta software, then I read the article...

    An attacker could exploit the flaw by crafting a special Web page that could be used to crash the browser or gain complete control of a vulnerable system

    So, this is actually a relevant article, despite its initial appearance.

    We've got some new additions and enhancements to IE, and here we have a flaw that can give an attacker complete control over the user's computer!

    I guess this is a taste of things to come in Vista? Evidence that Microsoft's secure code development practices are mostly just verbal pacification?

    1. Re:Nasty security flaw that Microsoft missed by blowdart · · Score: 2, Insightful
      We've got some new additions and enhancements to IE, and here we have a flaw that can give an attacker complete control over the user's computer!

      Actually you don't. There's a flaw that can crash the browser, but the reporter of this offers no proof that it will result in code execution or the ability to take over a user's computer. Very few buffer overruns result in code execution, and without proof, it's just another crash.

      Looking at how the reported went public before the vendor has a chance to respond it looks, to me, like someone attention whoring.

    2. Re:Nasty security flaw that Microsoft missed by zootm · · Score: 3, Interesting

      Fairly official response (taken from another comment).

      We received reports this morning that a security researcher had found a bug in the IE7 Beta 2 Preview release. This issue reportedly crashes IE and is exploitable to execute arbitrary code on the user's computer. Naturally, we take the security of IE and our users' safety very seriously, so we investigated immediately. We did confirm that the bug crashes IE. However, we did not find that the bug was exploitable by default to elevate privilege and run arbitrary code.

      This bug had already been found during our code review and analysis that is a mandatory part of our development process; it was scheduled to be fixed before our next public release. We do not believe this bug is easily exploitable, and as an extra defense, the /GS flag also catches the overrun. This is a compiler flag that tells Windows to watch for some classes of buffer overflows. If Windows sees a problem, it kills the application, in this case IE, instead of running the exploit code. While this is certainly not our primary line of protection, it does offer defense-in-depth to help keep our customers secure.

      So it appears that Microsoft's new development practices caught this bug internally before it was caught in the public beta, to find bugs like this. It also seems that the overrun is caught and dealt with (causing a crash as overruns should, but not allowing any degree of "control") by the system they are using for development anyway. Apparently the original article has not proven that the bug could be exploited at all yet anyway, so a response from his end will be required before this can really be seen as anything other than the sort of thing that's to be expected from a beta release.

  16. Error in article... by Linker3000 · · Score: 2, Funny

    Microsoft had no immediate comment on Ferris' alert.

    Not so - they tried to post a reply on his site but their browser kept crashing.

    --
    AT&ROFLMAO
  17. Re:Note: Its BETA by xtracto · · Score: 2, Insightful

    Oh come on. Its Google. Don't expect it not to have bugs. All its products are BETA.

    There you go, I corrected it for you. (no karma bonus checked for all those Gzealots)

    --
    Ubuntu is an African word meaning 'I can't configure Debian'
  18. Using beta for banking by ben_1432 · · Score: 3, Informative

    What kind of dumb-ass uses a beta browser for their banking anyway? It's not going to kill them to flick back to whatever their regular (non-beta) browser is.

    I don't just mean IE either. Firefox in it's pre 1.0 days had a bug where tabs could read form data from other tabs. Like credit card numbers. All the way up to 1.0.

    Why aren't beta's being released with some sort of self-setting desktop wallpaper that says "Look dipshit this is a beta product, and not like Google Beta TM, like buggy beta, so spare a seconds thought before you go doing your finances".

    In next weeks news: some stupid fuck loses his identity and $20000 minutes after using IE7 Beta to pay his bills, therefore IE7 is bad.

  19. MSIE 7 in the wild by harmonica · · Score: 3, Interesting

    Just looked at my logs for the last two days and MSIE 7 has already caused more requests than Opera/8, making it the #4 after MSIE 6, Mozilla and MSIE 5 (yes, grouping could be better for the Mozilla/Firefox family). It's a tech site, so the early adopters can be expected to show up here. Still, that was fast.

  20. The Acid 2 CSS Test by dshannon · · Score: 3, Insightful

    The famed acid2 test renders truly badly: http://www.webstandards.org/act/acid2/test.html#to p

  21. Safest Browser ever by stevea1210 · · Score: 2, Funny

    I installed it the other day, and it was the safest browser I ever used, seriously. I couldn't get it to work with our proxy, so I could only browse the corp intranet. Amazingly, I didn't get infected by any malware.

  22. MS Mantra: "Make the customer pay." (Repeat.) by zenwarrior · · Score: 2, Insightful

    Microsoft once again found itself playing catchup, this time in the browser market [again]. And with virtually all firms, that means a product often gets pushed out the door too quickly. That is clearly the case with I.E.7 (a.k.a. Deep-Six 7).

    This release qualifies as no more than an alpha. Anyone who feels otherwise has either done little beta testing, or refuses to open their eyes. (And no, I am not a MS basher. In fact, I still use IE6.) Think about it. It's been over a year since Firefox began stealing market share. Microsoft saw (and clearly thought) it could wait no longer, even if the release was far from ready. They simply had to get "a new browser" on the market.

    It may backfire, however. I tried Deep-Six 7, saw it was only an alpha, attempted to uninstall it, and then found it left my system in tatters! A beta should not do that; an alpha well may, however.

    Microsoft sees its customers as guinea pigs, at least in this case. There is no way that junk should have been released on an unsuspecting public. Many here clearly forget that only 1% of computer users are geeks. The rest are "normal people." The latter will see a download available and simply get it, with no thought [knowledge?] of what they're actually doing. Microsoft should remember that itself.

    I'm certain there were heated discussion about releasing it now (for marketing purposes) or holding off (for better quality before any public release). And now, the quality assurance folks are saying, "I told you so." This release has only further tarnished Microsoft's image as an innovative and quality-focused company. Instead, it now appear to be a behemoth that can barely move its own weight around, and certainly not nimbly keep up with its major competitors.

    --
    /.'s Psychic-in-Residence: Psychic to the Geeks
  23. From the IE Team Blog by Pedrito · · Score: 3, Insightful

    Finally, I'd like to reiterate the importance of the responsible disclosure of security issues. We firmly believe that privately disclosing security issues to software vendors is the best way to keep the users of the world secure.

    I'm sorry, but I take issue with this, particularly with a product being beta-tested, but really, with any product. Users need to know what exploits are known. If there are serious, known, security flaws in IE, that may very well affect my decision of whether or not I want to install it on my system. THe idea of keeping it hush-hush doesn't really help anyone.

  24. Gee, its BETA SOFTWARE! by TheSkepticalOptimist · · Score: 2, Insightful

    I know many people will just jump down Microsoft's throat for anything they do, they aren't my favourite company either. But I can't be sympathetic to people that complain about beta software.

    1) NOBODY is forcing you to install a beta product. If you are curious or impulsive, and feel compelled to install beta software, your doing so at great risk to your security and data. Whether it's Microsoft beta's, Google beta's, or Linux Beta's, you are accepting that risk by the nature of installing beta software (its in the disclaimer)

    2) THE REASON for beta software is to open it up to wider testing to CATCH AND FIX Bugs. This is a good thing, that bugs are flowing back to Microsoft. It will force them to fix the bugs and strengthen the product.

    3) No, you CAN'T Sue, see 1)

    4) Get a life. I mean, if IE 7 was in full release and these bugs were being reported, I would jump on the bandwagon myself and fire a few shots at MS, but this is still beta software, it isn't even a release candidate yet. Its intended for people with a brain to install it at their own risk and test the product, to REPORT bugs is the definition of what Beta software is. Obviously lots of stupid people are installing IE 7!

    This is NOT NEWS, this is sad. To report and complain that Microsoft's beta software is full of bugs suggest a complete bias, prejudice, and ignorance towards them without merit or provocation. This is not microsoft screwing up, this is microsoft doing what countless other software companies do, release a beta in order to get feedback and bug reporting in order to fix and strengthen the product.

    When FireFox 1.5 beta was released, it was full of bugs, but people praised Mozilla for their innovation and success. I can't stand double standards.

    --
    I haven't thought of anything clever to put here, but then again most of you haven't either.
  25. Re:Ahh... what a relief... by Kirsha · · Score: 4, Funny

    Yes, specially since Firefox never had any bugs!

    Right?

  26. XHTML support by Xugumad · · Score: 3, Informative

    IE still lacks XHTML support of any kind - I don't want to seem picky here, but it has been 6 years. Sure, I can have applications I work on spit out XHTML that's mostly like HTML 4, and send the appropriate MIME type based on the Accept header, but I'd really quite like to see IE support vaguely recent standards, y'know...

  27. Bill not a programmer? by blakespot · · Score: 2, Insightful
    Calling Tom Ferris a "Security Researcher" is like calling Bill Gates a programmer...

    • Why don't you sit down and code a BASIC interpreter for the MITS Altair on punch tape, asshat. Bill may be many things but he's busted out enough hardcore coding in years past to never lost the title of skilled coder.


    blakespot

    --
    -- Heisenberg may have slept here.
    iPod Hacks.com
  28. Report Non-Compliance As A Bug by Xopl · · Score: 3, Insightful

    I'm really serious about this... I'm not kidding...

    The web community should start flooding the bug reporting for the IE beta with reports about CSS and XHTML/HTML standards non-compliance. Anything IE 7 does that isn't in line with web standards should be reported as a bug, by as many people as possible. And we should keep reporting these, daily, until the IE team wakes up to web standards and decides to support them.

    Then, webmasters can make one version of the website that works in all modern browsers. Oh happy day. The IE team won't have to worry about supporting the weird IE quirks... people who haven't upgraded and are still using IE 6 will continue getting the same hacks that fix IE 6 and are ignored by Firefox et al, and IE 7 can ignore them just the same.

    Seriously... it's best for everybody.

    What's really going to piss me off is when they "fix" the hacks but not the non-compliance... AND on top of it they support some CSS 3 stuff in a non-standard way so we can go through this all over again when IE 8 comes out.