Updated: Internet Explorer 7 Deployment Guide

re: Updated: Internet Explorer 7 Deployment Guide

EricLaw [MSFT] — Tue, 22 Jan 2008 01:50:08 GMT

Thanks, Whitemarker. This is a known issue http://support.microsoft.com/kb/927917/en-us

re: Updated: Internet Explorer 7 Deployment Guide

whitemarker — Tue, 22 Jan 2008 01:32:08 GMT

I found a bug in IE 6 and 7 that should be fixed by IE 8. Where can I post it?

I have provided information on how to reproduce it:

http://whitemarker.blogspot.com/2008/01/ie-errors.html

re: Updated: Internet Explorer 7 Deployment Guide

Meubelstoffering — Sat, 19 Jan 2008 12:35:16 GMT

Good to know. Thanks for the info, I'm waiting for IE8 :).

Read past the headlines - Firefox is fixed faster

truth in statistics for once — Fri, 18 Jan 2008 17:42:03 GMT

Read past the headlines - Firefox is fixed faster

http://blog.mozilla.com/security/2008/01/17/read-past-the-headlines-firefox-is-fixed-faster/

The "inside job" Vulnerability report that was posted here on the IE Blog:

http://blogs.msdn.com/ie/archive/2007/11/30/the-first-year-of-ie7.aspx

Tried to make it look like Microsoft was on top of the security game. They were severely reprimanded by the community for not sourcing the document, and then later for "adjusting" the numbers.

The report by Secunia (see here)

http://secunia.com/gfx/SECUNIA_2007_Report.pdf

Has a nice little chart (Page 7, Fig 2) that paints the complete picture of the Windows URI handling bug, that Mozilla patched on their products, because Microsoft was (a) not claiming any responsibility, and (b) THREE months away from patching in Windows.

Care to comment? This isn't anything about IE8, so surely you can push those NDA's out of the way to chat about IE6, and IE7?

Ignoring The Community - Again

Kevin — Fri, 18 Jan 2008 14:22:18 GMT

Reading this blog has once again put me in a ranting mood... all because this blog just doesn't open up.

So here goes.

01.) MSDN Documentation. If you are not going to fix every method and property in IE that is broken in your JavaScript API's, then the LEAST you can do, is provide a "Known issues" section that indicates all the bugs/deviations from the published specifications.

i.e. There should be about 4 pages worth of "deviations" for the Element.setAttribute(name, value); Method.

If the implementation doesn't follow the specs - fine. But be (Wo)Man enough to admit your shortcomings and help developers out that are struggling to figure out why some of their calls work, and others don't.

02.) This Blog. If you end another post with "more to come", "more coming soon", or any line similar to that, IT MEANS YOU HAVEN'T INFORMED US ENOUGH of what you are talking about. Post your follow up within 2 days please.

03.) "IE8 Standards Mode" - You don't need to give out the trigger code for this yet, but to calm everyone down, an explanation of this would certainly help. Is this the DOCTYPE switch? or is this a 3rd rendering mode, triggered by an Opt-In statement.

04.) By now, there must be more fixes/features in IE8 that you can discuss. Please do so, no matter how minor they may seem.

05.) Bug Tracking System. Seriously. What's the hold up here? Come clean, is there, or isn't there going to be one, and when. THIS ISN'T HUMOROUS ANYMORE!

Kev

re: Updated: Internet Explorer 7 Deployment Guide

grhayes — Fri, 18 Jan 2008 09:27:15 GMT

Apparently I am not the only one tired of the way MS does business with IE. They seem to think standards are made for everyone else but them.

As one person pointed out I also have seen the number of IE drop on the site. I am at the point I no longer feel it is worth writing extra code to support the failure of such a blunder ware. Apparently a few friends of mine at some very large sites are also of the same mind. Most users are willing to at least use Firefox and when given the facts of how much faster it is and more compliant and .... Well they are almost eager to get it. I would rather pay to ship my customers a CD with firefox on it if need be than keep supporting every peace of code just to support a failure of a software.

It cost extra man hours just to maintain it or implement it for new features.

The way things are going XP will be the last OS I purchase from MS as well. I would rather start smoking, it would be healthier for me than dealing with the headaches like having the system decide it wants to install updates. So far I have been lucky to have saved. Frankly. I no longer will register as an MS developer. My servers are all now on Linux and 50% of the desktops are and figure by next years end all will be at the rate MS is going.

To look at the facts you got about 1/3 the world populace that is just going to be getting able to have a PC in the next few years none of which can afford windows. Wander what OS they will choose and what browser? Unless MS is planning on giving their OS away to 3rd world countries in a few years they will be number two in the OS game.

re: Updated: Internet Explorer 7 Deployment Guide

yan — Fri, 18 Jan 2008 04:50:39 GMT

Deployment may refer to:. System deployment, transforming a mechanical, electrical, or computer system from a packaged form to an operational state.

<a href="http://www.topgiftcn.com">thank</a>

re: Updated: Internet Explorer 7 Deployment Guide

Charlie — Fri, 18 Jan 2008 02:00:57 GMT

@Jote & s

Yes, it has been pointed out in not-so-official places all over the web. (we would like the IE Team to tell us, but they blog about as often as I get a haircut!)

Over on Molly's blog:

http://www.molly.com/2007/12/19/yes-ladies-and-gentleman-we-have-a-smiley/#comment-888632

Edward O'Connor points out, that in the HTML WG discussions, MS employees were significantly worried about compatibility, and didn't want to fix the "current" standards mode, because that would break sites expecting the broken behaviors.

And the debate heats up down further:

http://www.molly.com/2007/12/19/yes-ladies-and-gentleman-we-have-a-smiley/#comment-943419

And over on Chris Wilson's Blog:

http://blogs.msdn.com/cwilso/archive/2007/12/19/not-that-you-need-me-to-tell-you-this.aspx#6826941

which mentions the video (trying to dig it up, but I do recall it)

re: Updated: Internet Explorer 7 Deployment Guide

Fri, 18 Jan 2008 01:14:34 GMT

Ditto, is it stated anywhere EXPLICITLY that this is a third separate mode? If not, the way I see it the phrase "IE8 Standards Mode" can be interpreted as either

1. A separate mode, parallel with the "IE7 standards mode"

2. IE7 standards mode with more fixes

Stop whining about it; Did Firefox 1.5 pass Acid2? No. Did FF2? No. Does FF3? Yes. Do we have to use different "standards modes" in FF? No. Do we fix our CSS for FF3, because it passes Acid2 and FF2 doesn't? No. Get over it.

re: Updated: Internet Explorer 7 Deployment Guide

Jote — Thu, 17 Jan 2008 16:21:37 GMT

Does anyone have any proof that the "IE8 standards mode" is really a seperate THRID mode, instead of just the IE7 standards mode fixed?