Thread

Internet Explorer 9 Beta Released!

Will only run on:
Windows Vista and Windows 7.

Windows XP is DEAD!

Download Internet Explorer 9 Beta

InsiteFX

Cheers! Here’s hoping that we don’t need to much time updating our apps and websites 😛

edit: Crap I run Linux, with XP on a VM… this beta version needs vista or higher… :(

Fast when it works, but I am getting soem funnies, like clicking on a link, and nothing happens! Just shows the same page again…

Mat-Moo,

They said that there maybe problems with some websites
out there, until they update the source to IE 9.

To get around the bad sites click F12 IE Developer Toolbar.

You can then switch to IE 7, IE 8 or IE 9.

InsiteFX

This was on the default MSN page, no links would work! I’d even type a web address, and it would think for a few seconds, show it’s done and I’d still be stuck on the MSN home page. That dev tools is neat though, and today it does seem to be behaving a bit more 😊

Its a bit buggy but I am very impressed. Once the kinks are ironed out it very much looks like Microsoft have created a browser that I would actually be happy to use.

Currently, no matter what computer I use, if there is only IE I download anything else then uninstall when I am done. I can’t stand IE6/7/8. IE9 though… tis wonderful.

I have huge issues with javascript editors an IE9. The editor itself works, but it doesn’t populate the textarea in the form when you submit it, which renders the application useless for IE9 users.

Still trying to figure out what the issue is… :(

Mat-Moo,

I did some research and found out that MS has not upgraded
all of here website and MSN is one of them having problems.

WanWizard,
I will check on this and see if I can find an answer for you
I know IE 9 has a new builtin js engine which maybe the problem.

InsiteFX

I’ve managed to fix the editor in question (HotEditor, a BBcode editor we use in the forum module).

Primary issue was sloppy programming. Instead of testing capabilities, it (like many js scripts) tests browser versions.

IE9 proves to be ‘to compatible’, which means I had to use the Mozilla code sections and not the IE code sections to get it back on track… 😊

Soon after releasing this platform preview, we received reports that some web-apps that
use the jQuery framework did not work correctly in the preview. We tracked the problem
to a specific jQuery API method that in some cases passed a caller provided value to
Object.prototype.toString without first checking if the value was null or undefined.
Specifically, some calls to this jQuery method:

isFunction: function( obj ) {
     return toString.call(obj) === "[object Function]";
},

failed with an exception: “TypeError: Object expected”. Further analysis showed that
toString in the above code was the built-in method Object.prototpe.toString and that the
failures occurred when isFunction was being called with undefined as its argument. Why
does an exception occur in IE9 and not in previous versions of IE or other browsers? It
is because the third IE9 Platform Preview in standards mode actually conforms to the ES5
specification for Object.prototype.toString.

According to the prior editions of the ECMAScript specification, calling any built-in method using null or undefined as the this value passes the “global object” (in browsers this is the DOM window object) to the method as its this value.  This opens a number of potential security holes for frameworks that aim to support mash-ups in a secure way.

The ES5 specification changed this so that null or undefined is not replaced with the window object and the definition for each built-in method was updated specifically to deal with receiving these values as their this value. The ECMAScript technical committee tried to do this in a way that preserves backwards compatibility for normal usage and throws an exception in cases where that is not possible. Object.prototype.toString was specified in ES5 to throw such an exception. This created the compatibility problem described above.

This problem can be easily corrected by modifying the jQuery code with the additions shown in red:

isFunction: function( obj ) {
     return [color=red]obj &&[/color] toString.call(obj) === "[object Function]";
},

The jQuery team actually intends to make this change. However, such a change will not
correct the thousands of locally hosted copies of jQuery that already exist on the Web.
With the broad use of jQuery, it is clear that the ES5 specification contains a
significant compatibility problem. It is fairly obvious how we can modify the IE9 ES5
implementation to eliminate the problem. We can just return the same string value
(”[object Object]”) that IE8 returns in this situation. Such a fix does not reintroduce
any of the security problems that ES5 strives to eliminate. However, we do not want to
unilaterally introduce such a variation into our implementation of a new standard. It
does not help either compatibility or interoperability if IE fixes this problem one way,
and other browsers either don’t fix it or fixed it a different way.

IE9’s default UA string

There are four changes to IE8’s UA string that site developers need to be aware of:

Application version is incremented from ‘Mozilla/4.0’ to ‘Mozilla/5.0’ to match other browsers (explained well in the great History of the user-agent string post). This change signals that IE9 is an interoperable browser.
Version token is incremented from ‘MSIE 8.0’ to ‘MSIE 9.0’.
Trident token is incremented from ‘Trident/4.0’ to ‘Trident/5.0’.
IE9 will send the following short UA string without additions made by other software installed on the machine:

Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.0; Trident/5.0)

IEBlog

InsiteFX

One bug I did find after installing IE 9 on Windows 7 64-bit
was that my Addgadget CPU meter no longer worked!

I email them and within 24 hours the problem was fixed!!!

Now that’s what I call SUPPORT.

InsiteFX

Same issue for me 😊 I also emailed as well.

I liked the GPU render part.

But I love XP more than that.

Windows XP is DEAD! MS will no longer support it.

Plus it has offically KILLED! IE 6.

In other words soon you will see no more updates
to IE 6 or Windows XP.

Which means there will be security holes all over
the place.

InsiteFX

“soon” being 2014.